MCP Client Setup — Claude Desktop

Use the exact configuration shown on your tenant’s Settings → MCP page in the FlowState app. It is generated from your tenant’s live gateway URL and credentials, and is the source of truth if it ever differs from this page.

Add FlowState as an MCP server

1. In the FlowState app, go to Settings → MCP and copy the Claude Desktop snippet shown there.
2. Open the Claude Desktop configuration file:
   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json
   • Linux: ~/.config/claude-desktop/claude_desktop_config.json
3. Add the copied snippet to the mcpServers object and save.
4. Restart Claude Desktop.

The in-app snippet uses npx @anthropic-ai/mcp-client-sse against your tenant’s live gateway URL. If the in-app snippet ever differs from documentation you find elsewhere, the app is the source of truth.

Trigger the auth flow

1. In Claude Desktop, open a new conversation.
2. Type a message that uses a FlowState tool, for example: “List my FlowState tenants.”
3. If the connection method requires it, Claude Desktop opens your default browser to authenticate.
4. Sign in with your FlowState credentials (email + password or Google SSO).
5. The conversation continues — Claude calls list_my_tenants() on your behalf and shows the result.

Tenant context

There is no MCP-side tenant switch — select_active_tenant returns an unsupported-operation error rather than re-scoping your session (see MCP → Authentication). Set your active tenant in the FlowState web app before starting a Claude Desktop session that needs a specific tenant’s data.

Verifying the connection

Ask Claude: “What FlowState tools are available?” Claude lists the available tools from the FlowState MCP server. You can also ask: “Get my FlowState profile” to confirm you are authenticated and see your current tenant context.

Token refresh

Where the connection method supports it, Claude Desktop refreshes the access token automatically before its 60-minute lifetime expires. If the refresh token expires (30 days of inactivity), you will need to re-authorize.