MCP Integration

Use your preferred AI app to work with your Splice workspace. Ask it to review conversations, organise tasks, prepare campaigns, or test an agent, and it can use your workspace tools to do the work.

What is MCP?#

Model Context Protocol (MCP) connects AI apps to tools and data. Splice provides a remote MCP server that your AI app can connect to using your Splice account. You choose the workspace and permissions during sign-in.

Connect directly

You can use the MCP server without installing a Splice plugin package. Add the server URL to a compatible AI app and sign in through Splice.
https://spliceai.co/mcp

Before you connect#

  • A Splice account with access to an active workspace.
  • MCP beta access enabled for that workspace. Contact Splice support if it is not enabled.
  • An AI app that supports remote MCP servers and OAuth sign-in. Your app's plan and administrator settings may affect availability.

The connection follows your existing workspace permissions. Channels and tools also need their usual setup before they can perform actions. Agent tests and other AI-backed actions use your Splice credits.

Connect your AI app#

ChatGPT

  1. 1Open ChatGPT's apps or connector settings and choose the option to add a custom MCP server. This may require developer mode, depending on your account.
  2. 2Name the connection Splice AI and enter https://spliceai.co/mcp as the server URL.
  3. 3Choose OAuth authentication and the automatic registration option if one is shown. Sign in to Splice, choose your workspace, and allow the permissions you want to use.
  4. 4Enable the Splice connection in a conversation and ask it to identify your workspace.

Claude

  1. 1Open Customize → Connectors and choose Add custom connector.
  2. 2Name it Splice AI and enter https://spliceai.co/mcp.
  3. 3Start the connection and sign in to Splice. Choose your workspace and review the requested permissions. Leave custom OAuth client credentials blank when using automatic registration.
  4. 4Enable Splice in a conversation and ask it to show your workspace and tasks.

Cursor

  1. 1Open Cursor's MCP settings and add a custom server, or edit .cursor/mcp.json in your project.
  2. 2Add the configuration below, save it, and start the Splice server from Cursor's MCP settings.
  3. 3Complete OAuth sign-in in Splice, then enable the Splice tools in your agent conversation. Leave static OAuth credentials unset for automatic registration.
{
  "mcpServers": {
    "splice": {
      "url": "https://spliceai.co/mcp"
    }
  }
}

Cursor MCP documentation

VS Code with GitHub Copilot

  1. 1Open the Command Palette and run MCP: Add Server.
  2. 2Choose HTTP, enter https://spliceai.co/mcp, and name the server Splice AI. Choose where to save the configuration.
  3. 3Start the server and complete OAuth sign-in when prompted. In Copilot agent chat, enable the Splice tools from the tools picker.

VS Code MCP documentation

Claude Code

Register the remote server from your terminal:

claude mcp add --transport http splice https://spliceai.co/mcp

Run /mcp in Claude Code, select Splice, and follow the authentication prompt. Sign in to Splice and choose your workspace and permissions. You can then use the connection in Claude Code, including its IDE integration.

Claude Code MCP documentation

Windsurf / Cascade

  1. 1Open the MCP configuration from the Cascade panel's MCP settings or Actions menu.
  2. 2Add Splice under mcpServers using the configuration below and save the file.
  3. 3Refresh the server list, enable Splice, and complete OAuth sign-in. Your editor version and team policy must allow remote HTTP MCP servers.
{
  "mcpServers": {
    "splice": {
      "serverUrl": "https://spliceai.co/mcp"
    }
  }
}

Windsurf / Cascade MCP documentation

Codex

Add a remote HTTP MCP server using the same URL, then start OAuth login from your app. Compatible desktop clients register their local callback automatically. In Codex, the server configuration can be as small as:

[mcp_servers.splice]
url = "https://spliceai.co/mcp"

The configuration format varies by app. Use its remote HTTP transport and OAuth login controls. You do not need to paste your Splice password, a bearer token, or a shared client secret into the configuration.

Other compatible IDEs and MCP clients

Splice uses the standard remote MCP protocol. In another IDE or AI app, addhttps://spliceai.co/mcp as a remote HTTP server and use its OAuth login flow. An IDE needs an MCP-capable agent or extension with remote HTTP and OAuth support; local-only or API-key-only MCP clients cannot connect through this flow.

What you can do#

Workspace areaExample work
ConversationsReview inbox threads, inspect drafts, and find conversations that need attention.
Tasks and leadsList and update tasks, add comments, review leads, and organise follow-up work.
AgentsInspect instructions and channel readiness, update permitted settings, and run playground tests.
CampaignsPrepare email or WhatsApp drafts, review audiences, and check campaign results.
Knowledge and workflowsInspect knowledge-base content, edit permitted Pulse flows, and check workflow readiness.

Available tools depend on the permissions you grant, your role, enabled workspace features, and connected channels. The AI app can check what is ready before attempting an action and explain any setup it still needs.

Try your first prompts#

Start with a read, then try a small draft or task:

  • Show my connected Splice workspace and tell me what you can do.
  • Review my conversations and list anything that needs my attention.
  • Create a task called Review MCP setup, due tomorrow.
  • Draft a welcome email campaign for my new leads and show me what is still needed before sending.
  • Test my agent with a normal pricing question and a request for a discount. Explain where its replies need improvement.

Give it the outcome

Describe what you want to achieve. The AI app can discover the available tools, inspect the relevant records, and ask for missing details. You do not need to name individual MCP tools in your prompt.

Permissions and approval#

At sign-in, select the workspace and access you want to grant. Write permissions are unchecked by default. Select all available chooses only permissions your current role allows. The connection can never access another workspace through that grant.

Drafting a campaign is separate from sending it. Customer sends and Pulse activation require a review in Splice before execution. Your AI app returns a review link so you can inspect the exact action and approve it. If the content or recipients change, the action needs a fresh review.

To add permissions later, reconnect and select the additional access. Changing your role, removing workspace membership, or disabling MCP beta access also affects the connection.

Troubleshooting#

What you seeWhat to check
Access deniedConfirm that the workspace is active, you are a member, and MCP beta access is enabled. Contact Splice support for beta access.
Connection or registration errorCheck the server URL, update your MCP client, and restart its OAuth connection. Remove conflicting old predefined client settings when switching to automatic registration.
A tool is missing or permission is deniedCheck your workspace role and the permissions selected during sign-in. Reconnect to grant additional permitted access.
A channel or sender is unavailableConnect the required channel in Splice and check the agent's channel readiness before requesting a send.
Insufficient creditsAdd Splice credits before running agent tests or other metered AI actions.
Expired or revoked connectionStart OAuth login again. If a workspace administrator removed your access, resolve that before reconnecting.

If the issue continues, contact support@spliceai.cowith your AI app name and the error message. Keep passwords and access tokens out of your message.

Manage your connection#

Open Settings → Connectors in Splice to review and disconnect your connections. Disconnecting revokes that connection's workspace access. Remove the connection from your AI app as well if you no longer want it listed there.