Dapple's MCP server lets you connect Claude, ChatGPT, Cursor, or any other MCP-compatible AI client directly to your organisation's Dapple data. Turn on MCP enabled in your organisation settings, then add Dapple's MCP URL (https://app.dapplehq.com/api/mcp) to your AI client and complete Dapple's OAuth sign-in to approve access for your organisation. Once connected, enable Dapple for a specific conversation and your AI tool can read and act on your organisation's data using your existing permissions. If your tool doesn't support OAuth, you can authenticate with a Dapple API token as a Bearer token instead.
What is Dapple's MCP server, and what does it let me do?
Dapple's MCP server exposes your organisation's Dapple data to AI clients that support the Model Context Protocol (MCP), an open standard for connecting AI assistants to external tools and data. Once connected, an AI client such as Claude, ChatGPT, or Cursor can read and interact with your organisation's Dapple data on your behalf, inside a normal chat, instead of you switching back to the Dapple app.
How do I enable MCP for my organisation?
MCP access is off by default and controlled at the organisation level.
Open your organisation settings and go to the AI tab
Select the MCP option.
Toggle MCP enabled on.
This allows MCP clients using your organisation's API tokens to use the Dapple MCP server. Turn this off at any time to block all MCP tools from accessing the organisation, regardless of which clients are already connected.
How do I connect Claude to Dapple?
Claude Desktop and claude.ai connect to Dapple as a custom connector.
Open Claude and go to Customize > Connectors.
Select +, then Add custom connector.
Paste the Dapple MCP URL (https://app.dapplehq.com/api/mcp) and add it.
Select Connect and complete the Dapple OAuth sign-in and organisation approval.
Start a chat, open the + menu, choose Connectors, and enable Dapple for the conversation.
How do I connect ChatGPT or another OpenAI client to Dapple?
ChatGPT connects to Dapple through Developer Mode, which is available on paid ChatGPT plans and is turned on per workspace.
Ask your workspace admin to enable Developer Mode for custom MCP apps.
Open Workspace Settings > Apps > Create, then provide the Dapple MCP URL (https://app.dapplehq.com/api/mcp).
Choose OAuth as the authentication method and complete the Dapple authorisation prompt.
Select Scan Tools, review the tools and permissions, then create the app.
An admin or owner must publish the app before it's available to other workspace members.
Open a chat, select Dapple from the tools menu, and approve tool calls when prompted.
For the OpenAI Responses API, configure the same URL as an MCP tool and provide the OAuth access token in the request's authorization field.
How do I connect Cursor to Dapple?
Cursor connects to Dapple as a remote MCP server.
Open Cursor Settings and go to Tools & Integrations > MCP.
Add a custom or remote MCP server and paste the Dapple MCP URL (https://app.dapplehq.com/api/mcp).
Save the server, then select Connect or Authorize if shown.
Complete Dapple OAuth, choose the organisation, and approve the requested access.
Check that Dapple is marked connected and its tools are listed before using it in Agent mode.
How do the three setup flows compare?
All three clients use the same Dapple MCP URL and the same OAuth approval step, but the entry point differs.
Client | Where you add the URL | How you authenticate |
Claude | Customize > Connectors > Add custom connector | Dapple OAuth, via Connect |
ChatGPT / OpenAI | Workspace Settings > Apps > Create (Developer Mode) | OAuth, reviewed via Scan Tools |
Cursor | Cursor Settings > Tools & Integrations > MCP | OAuth, via Connect / Authorize |
What happens during Dapple's OAuth approval step?
When you select Connect (or the equivalent action in your client), Dapple opens a sign-in window. Sign in to your Dapple account, choose which organisation to connect if you belong to more than one, and approve the access being requested. Your AI client can then act using your organisation's existing permissions — it doesn't gain any access you wouldn't otherwise have inside Dapple.
Can I connect a client that doesn't support OAuth?
Yes. If your AI client doesn't support OAuth, use a Dapple API token as a Bearer token instead of going through the sign-in flow. Add the token to your client's authorization header in place of the OAuth flow described above.
Best practices for connecting AI clients to Dapple
Only turn on MCP enabled for organisations that actually need AI tool access — leave it off otherwise.
Treat a Dapple API token used as a Bearer token like a password: it's scoped to your organisation's data, not just your own account.
During the OAuth consent screen, only approve the scopes and organisation you intend to connect.
Check that your AI tool can reach https://app.dapplehq.com/api/mcp over HTTPS before troubleshooting further — remote clients need a publicly reachable URL, not a local one.
Review which AI tools are connected periodically, and turn off MCP enabled if you stop using AI integrations.