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.
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
https://spliceai.co/mcp
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.
https://spliceai.co/mcp as the server URL.https://spliceai.co/mcp..cursor/mcp.json in your project.{
"mcpServers": {
"splice": {
"url": "https://spliceai.co/mcp"
}
}
}MCP: Add Server.https://spliceai.co/mcp, and name the server Splice AI. Choose where to save the configuration.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.
mcpServers using the configuration below and save the file.{
"mcpServers": {
"splice": {
"serverUrl": "https://spliceai.co/mcp"
}
}
}Windsurf / Cascade MCP documentation
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.
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.
| Workspace area | Example work |
|---|---|
| Conversations | Review inbox threads, inspect drafts, and find conversations that need attention. |
| Tasks and leads | List and update tasks, add comments, review leads, and organise follow-up work. |
| Agents | Inspect instructions and channel readiness, update permitted settings, and run playground tests. |
| Campaigns | Prepare email or WhatsApp drafts, review audiences, and check campaign results. |
| Knowledge and workflows | Inspect 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.
Start with a read, then try a small draft or task:
Give it the outcome
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.
| What you see | What to check |
|---|---|
| Access denied | Confirm that the workspace is active, you are a member, and MCP beta access is enabled. Contact Splice support for beta access. |
| Connection or registration error | Check 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 denied | Check your workspace role and the permissions selected during sign-in. Reconnect to grant additional permitted access. |
| A channel or sender is unavailable | Connect the required channel in Splice and check the agent's channel readiness before requesting a send. |
| Insufficient credits | Add Splice credits before running agent tests or other metered AI actions. |
| Expired or revoked connection | Start 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.
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.