Connected Apps is the RichAPI dashboard page that lists every AI client authorized to call RichAPI tools through MCP. Each row shows the client name, the client host, the connect date, and the last active time. Every active connection has a Rename button and a Disconnect button.

A connected app is one AI client that a workspace member authorized through the RichAPI OAuth consent screen. Claude Desktop, Claude Code, Cursor, and Windsurf are connected apps. RichAPI creates one row for each authorization. When the same member authorizes the same client again, the new row replaces the old one, and the old row moves to Revoked. Every request that a connected app sends is billed to the organization balance, through the workspace that owns the connection.

RichAPI accepts any MCP client that supports the remote HTTP transport. The MCP Setup page names four options.

RichAPI holds no fixed allowlist of clients. The name in the list comes from the client_name field that the client sends during dynamic client registration (RFC 7591). If the client sends no name, RichAPI derives the name from the redirect URI.

CAUTION: Create an API key before you start. When the account has no active API key, the consent screen refuses the authorization.

The consent screen is titled Connect RichAPI. It names the client under Requesting access. Under Signed in as, it shows your email address, the workspace name, and Using API key with the prefix of the API key that the connection will use. A note states that the connection has the same access as that API key, and that revoking the key disconnects the client too.

The two buttons are Deny and Allow.

RichAPI supports one scope. The MCP server advertises scopes_supported: ["mcp"] in both /.well-known documents. A client that sends no scope receives mcp.

RichAPI stores one record for each authorization. Each row on the Connected Apps page shows these details.

RichAPI also records the member who authorized the connection. The page does not show it.

A workspace with at least one revoked connection also shows a Revoked section. An active row carries a Connected badge. A revoked row carries a Revoked badge and shows the disconnect date.

When the workspace has no active connection, the page shows this text: "No active connections. Go to Claude Desktop / Cursor / Windsurf, add a Custom Connector with the URL https://mcp.richapi.ai/mcp, and follow the sign-in flow to authorize your first connection."

When two members connect the same client, both rows carry the same name. A label tells them apart.

The dialog rejects an empty name with the message Name cannot be empty. It rejects a longer name with the message Name must be 80 characters or fewer.

CAUTION: Disconnect an app only to stop its calls. The AI client loses every RichAPI tool and returns an error until a member authorizes it again.

The confirmation dialog reads: "Disconnect this app? Its access to your RichAPI account will be revoked shortly and may take up to about a minute to fully take effect."

A second disconnect on the same connection returns success and changes nothing.

A disconnect marks the connection as revoked. The MCP server caches the "not revoked" verdict for 60 seconds. A tool call that already passed the check runs to the end. The next call fails after the cache expires.

RichAPI cannot re-enable a revoked connection. Authorize the client again to restore access.

A client that sends the RichAPI API key in an x-api-key header creates no connection row. That client never appears on the Connected Apps page, and a disconnect does not stop it. To stop that client, revoke its API key on the API Keys page.

Connections are scoped to a workspace. Every member of that workspace sees every connection and can rename or disconnect any of them. The owner role is not required.

The consent screen binds the connection to the workspace that holds your most recently created active API key, across all your workspaces. A user who belongs to several workspaces must check the workspace name on the consent screen before the approval.

The connection record holds no API key and no readable token.

A connected app costs nothing. RichAPI charges credits for the tool calls that the app sends, at the same price as a direct API call. 1 credit costs $0.02 on the 1,000 and 5,000 credit packs, and less on larger packs.

The enrich_profile tool costs 1 credit per call, or 2 credits when the call asks for social metrics.

No. A disconnect moves the connection into the Revoked section of the Connected Apps page. The row stays visible with its connect date, its last active time, and its disconnect date.

A disconnect takes up to about one minute. The RichAPI MCP server caches the "not revoked" verdict for 60 seconds, so a tool call inside that window can still succeed. After the cache expires, the connection returns 403.

Yes. Connections belong to the workspace, not to the person who authorized them. Every member of the workspace can see, rename, and disconnect every connection in it. The owner role is not required.

No. The AI client receives an OAuth bearer token. The token works with the access of an API key of the workspace, but it does not contain the key. RichAPI stores only a hash of the token.

RichAPI supports one scope, named mcp. The MCP server advertises scopes_supported: ["mcp"] in its authorization server metadata and in its protected resource metadata. A client that sends no scope receives mcp.

Use the Rename button. The rename dialog sets a label of up to 80 characters on one connection. The row also shows the client host, which separates a desktop build from a local development build.

No. A connected app spends from the organization balance, through the workspace that owns the connection. The consent screen names that account before you click Allow.

Next: Receiving Outbound Webhooks