Skip to main content
The User Intuition MCP server is available at:
Compatible clients discover OAuth automatically. Complete the authorization flow before testing a tool. Seeing the tool catalog alone is not proof of authentication because a client can discover tools before an account-scoped request succeeds.

​
stdio clients

Claude Desktop, Cursor, Claude Code, and VS Code can launch the MCP server locally. Set USERINTUITION_API_KEY to a key created under Settings → API Keys. The key has the access of the account that created it. Keep API keys out of source control, screenshots, prompts, and shared configuration files. Rotate a key immediately if it is exposed.

​
Authorization behavior

Every backend request is scoped to the authenticated account. Resource reads, updates, and deletes also perform ownership checks. A valid OAuth session or API key can still receive 403 or 404 when the requested resource is not accessible.

​
External side effects

The surface includes paid panel launches, participant invitations, rewards, and completed-interview webhooks. Authentication makes those operations available; it does not replace product decisions or user confirmation. Agents must return and obtain approval of the current persisted plan before participant creation or paid launch, and respect each tool’s safety annotations before spending money, sending a reward, registering a webhook, stopping recruitment, or deleting data.