MCP

Assistants can use SignalDock through MCP (Model Context Protocol). After you connect and allow access, the assistant works with the same account and organization membership you use in the app (RLS-scoped tools).

The local MCP address is:

https://mcp.localhost

On the shared production host the path is /mcp (rewritten to the mcp service). Do not paste access tokens into a client. The assistant signs in through SignalDock’s consent screen (/oauth/consent on the SaaS app). Supabase Auth is the OAuth 2.1 authorization server (dynamic client registration on).

• Open in Cursor
• Open in Claude
• Open ChatGPT
• claude mcp add --transport http signaldock https://www.signaldock.dev/mcp

• Open in Cursor adds SignalDock in Cursor. Confirm the prompt, then sign in when Cursor asks.
• Open in Claude opens Claude with SignalDock already filled in.
• Open ChatGPT takes you to ChatGPT. ChatGPT has no one-click add; follow the steps below.

CursorCopy Anchor Link

1. Choose Open in Cursor above, or open Customize → MCPs and add a remote server yourself.
2. If you add it by hand, use the name signaldock and this address locally:

{
  "mcpServers": {
    "signaldock": {
      "url": "https://mcp.localhost"
    }
  }
}

3. When Cursor asks you to sign in, finish in the browser and choose Allow on the consent screen.

ClaudeCopy Anchor Link

claude mcp add --transport http signaldock https://mcp.localhost

On the web, Customize → Connectors → Add custom connector, then paste the MCP URL. Sign in and choose Allow when SignalDock asks.

ChatGPTCopy Anchor Link

Custom connectors need Developer mode on a paid plan.

1. Turn on Developer mode in ChatGPT settings.
2. Add a connector: Streamable HTTP, paste the MCP URL.
3. Leave bearer token / token env vars empty. Choose OAuth if the form has an authentication control.
4. Save, sign in, and enable the connector in a chat.

What the assistant can doCopy Anchor Link

Tools run with your membership and row-level security, so the assistant sees exactly what you see in the app.

Tools that start durable work (source runs, reprocessing, campaign proposals, enrollments, and approving or rejecting drafts) are forwarded to the API with your token, so they behave exactly like the app. Well-behaved clients ask you before calling an action tool; the instructions tell them to.

Creating organizations, changing scoring, and connecting mailboxes or CRMs still happen in the app. The in-app copilot uses the same tools.

If something goes wrongCopy Anchor Link

• The form asks for a bearer token. Leave it empty. SignalDock uses OAuth.
• Protected resource mismatch. Keep the MCP URL (/mcp in production, https://mcp.localhost locally). Discovery is served at /.well-known/oauth-protected-resource.
• The consent screen lists more access than you want. Choose Deny.