MCP server

​

Prerequisites

• OAuth (recommended for Cursor and Claude) — the client prompts you to sign in and approve scopes
• API keys — static bearer tokens for clients that do not support MCP OAuth, scripts, and server-to-server tools

​

Connect manually

• Claude Desktop
• Cursor
• API key

Remote MCP URL

https://app.forecastable.com/mcp

1

Open connectors in Claude

In Claude, open Customize in the sidebar, then go to Connectors.

Click the + button and choose Add custom connector.

2

Add the MCP server

In the Add custom connector dialog, set:

Field	Value
Name	Forecastable (or your preferred label)
URL	https://app.forecastable.com/mcp

Leave Advanced settings empty. Forecastable supports OAuth Dynamic Client Registration, so Claude registers an OAuth client automatically and receives a client ID and secret without showing them to you.

3

Authorize the connector

Open the Forecastable connector in Claude and click Connect.

Forecastable prompts you to sign in (if needed) and review the requested scopes on a consent screen. Click Allow to grant access. Claude exchanges the authorization code for an access token and uses it on later MCP requests.

4

Verify the connection

After authorization succeeds, test the connector in Claude. A good first check is to list organizations, choose one, and call a read-only tool such as listAccounts.Single-organization users can call account, contact, or plan tools immediately. If an organization is missing, the error lists accessible names and IDs; retry with params.organizationId.

​

Troubleshooting

Claude asks for a client ID and secret

Confirm you are using https://app.forecastable.com/mcp and that the Forecastable OAuth discovery endpoint is reachable at https://app.forecastable.com/.well-known/oauth-authorization-server. Claude should only require manual credentials if it cannot discover or call the dynamic registration endpoint.

Redirect URI mismatch

Claude dynamically registers https://claude.ai/api/mcp/auth_callback as its redirect URL. If you created an OAuth app manually, confirm that callback URL is listed exactly in Redirect URLs.

Invalid client or unauthorized

Disconnect and reconnect the connector so Claude can register fresh OAuth credentials. If you configured a client manually in Advanced settings, verify the client ID and client secret match the Credentials section for the same OAuth app.

Insufficient scope

Disconnect and reconnect the connector so Claude can request the updated permissions and you can approve them on the Forecastable consent screen.

Missing organization context

Your organization is selected automatically when you have access to exactly one. With multiple organizations, ask Claude to call listOrganizations and save your choice using setActiveOrganization.

Add to Cursor

Add a remote MCP server in your Cursor MCP configuration (.cursor/mcp.json or global MCP settings):

{
  "mcpServers": {
    "forecastable": {
      "url": "https://app.forecastable.com/mcp"
    }
  }
}

Cursor discovers Forecastable’s OAuth metadata, registers a client automatically, and prompts you to authenticate. Sign in to Forecastable (if needed), review the consent screen, and click Allow.

Use an API key when your MCP client does not support OAuth. Add the server with an Authorization header:

{
  "mcpServers": {
    "forecastable": {
      "url": "https://app.forecastable.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Replace the placeholder with your API key. To set an optional default organization, add "X-Organization-Id": "YOUR_ORGANIZATION_ID" to headers.

​

Available tools

​

Meta

​

Organizations

​

Accounts

​

Contacts

​

Opportunities

​

Leads

​

Relationship maps

​

Plans

​

Engage templates

​

Engage drafts

​

Engage lists

​

Engage campaigns

​

Engage queue (read-only)

​

Feed

​

Calendar

​

Authentication

Authorization: Bearer YOUR_API_KEY

• integration API keys issued from developer settings
• OAuth2 authorization-code access tokens issued after user consent
• OAuth2 client-credentials access tokens for server-to-server clients, where enabled

​

Organization context

1. Request header (recommended): X-Organization-Id: <uuid>
2. Tool input headers: { "headers": { "xOrganizationId": "<uuid>" } }
3. Query params in tool input: { "params": { "organizationId": "<uuid>" } }
4. Saved selection: for multiple organizations, call listOrganizations, ask the user which to use, then call setActiveOrganization. The choice is stored for this user and token and survives reconnects and new chats.

​

Sessions

​

Example tool call

{}

{
  "organizationId": "YOUR_ORGANIZATION_ID"
}

{
  "params": {
    "limit": 25
  }
}

​

Scopes

​

Rate limits

​

Troubleshooting

​

Related resources

• API reference — full Integration REST API documentation
• GET /meta — live metadata for auth, scopes, and limits