Connect MCP

Connect Falconer MCP to your AI client so it can search, read, create, and update Falconer documents.

Falconer’s MCP endpoint is:

https://falconer.com/api/mcp

When your client connects, it opens Falconer OAuth in your browser. Sign in with your Falconer account and approve the connection.

Sign up from your agent

You do not need an existing Falconer workspace to connect. If you are new to Falconer, the OAuth browser step lets you create an account (Google, GitHub, or email and password). Connecting automatically creates a workspace named after you, with a free Pro trial when available, and your agent can finish the rest of signup over MCP:

1. The agent reads the account settings scope to see the plan options, credit balance, and pricing.
2. The agent asks what you want to name your workspace and sets name in the org settings scope.
3. To pay as you go, the agent sets credits.purchase with the pack you choose and whether to turn on auto-reload; to subscribe, it sets plan to "pro". Either way it gives you a Stripe-hosted checkout link to open in your browser. Payment details are only ever entered on Stripe’s page, never in the chat.

The plans and credit packs are the same ones owners see in organization settings; see Plans and billing for what each plan includes.

Claude

Falconer supports both Claude.ai and Claude Code: add Falconer to Claude.ai as a custom connector, or configure Falconer in Claude Code from the command line.

Claude.ai

Add to Claude.ai

This opens Claude with the Falconer connector name and MCP URL prefilled. Connect the connector, then sign in to Falconer when Claude asks for authorization.

Manual setup:

1. Open Claude connectors.
2. Click Add custom connector.
3. Set Name to Falconer.
4. Set the MCP server URL to https://falconer.com/api/mcp.
5. Leave OAuth Client ID and OAuth Client Secret empty.
6. Click Add, connect the Falconer connector, and sign in to Falconer when Claude asks for authorization.

Claude Code

Run this command in a terminal:

claude mcp add --transport http --scope user --client-id falconer-claude-code --callback-port 49152 "falconer" "https://falconer.com/api/mcp"

Then open Claude Code and run:

/mcp

Follow the browser sign-in flow. If port 49152 is unavailable, change it to another local callback port and rerun the command.

Cursor

Falconer supports both Cursor surfaces: add Falconer to the Cursor app for editor workflows, or configure Cursor Agent for agent sessions.

Cursor app

Add to Cursor app

This opens Cursor with Falconer’s MCP configuration. Connect the Falconer server, then sign in to Falconer when Cursor asks for authorization.

For manual setup, create or update .cursor/mcp.json in your project:

{
  "mcpServers": {
    "Falconer": {
      "type": "http",
      "url": "https://falconer.com/api/mcp"
    }
  }
}

Open Cursor MCP settings and complete the Falconer OAuth flow if prompted.

Cursor Agent

Open Cursor Agent

1. Add a new MCP server named Falconer.
2. Use https://falconer.com/api/mcp as the MCP server URL.
3. Click Login to start the OAuth flow for Falconer.

Codex CLI

Falconer supports Codex CLI through an OAuth-backed MCP connection configured from the terminal.

Run this command in a terminal:

codex mcp add falconer --url "https://falconer.com/api/mcp" --oauth-client-id falconer-codex-cli --oauth-resource "https://falconer.com/api/mcp"

Verify the server is listed:

codex mcp list

Building an app or agent on Vercel? See Vercel Connect.

Disconnect MCP

Disconnect Falconer in two places if you want to fully remove access.

First, revoke Falconer-side authorization. Open Personal settings > Connected accounts, then disconnect the relevant MCP client. This revokes that client’s Falconer OAuth tokens, so it can no longer access Falconer using your account.

Then remove Falconer from your MCP client.

For Claude Code:

claude mcp remove falconer

For Codex CLI:

codex mcp remove falconer

For Cursor app, remove the Falconer entry from your Cursor MCP config or remove Falconer from Cursor MCP settings.

For Cursor Agent, remove Falconer from Cursor Agent MCP settings.

For Claude.ai, remove or disconnect the Falconer custom connector from Claude.ai connector settings.

For other clients, remove Falconer using that client’s MCP documentation.

Troubleshooting

Issue	What to do
Falconer tools do not appear after connecting	Fully restart your MCP client and start a new session. Reconnecting from /mcp does not always pick up the tools of a newly added or updated MCP server.
The client says authentication is required	Reconnect Falconer and complete the browser OAuth flow.
The client cannot choose an organization	Ask it to call list_organizations, then use the returned organizationId.
The token expired or was revoked	Reconnect Falconer from your MCP client.
Your client does not support Falconer MCP	Use Claude.ai, Claude Code, Codex CLI, Cursor, or another client that supports HTTP MCP. You can also use the Falconer CLI for direct command-line access.