SendPulse MCP Quickstart

Use this file when the task is specifically about connecting SendPulse MCP in a client and reaching the first successful tool call.

Official source of truth

• MCP setup guide: https://sendpulse.com/knowledge-base/account-settings/mcp-server
• MCP tools list: https://sendpulse.com/knowledge-base/account-settings/mcp-tools
• MCP product page: https://sendpulse.com/features/mcp

Before setup

Decide which client you are targeting:

• OpenAI / ChatGPT-style MCP client
• Cursor
• another MCP client

Do not assume the auth flow is identical across clients.

Get the MCP link

In SendPulse:

1. Open Account settings > API
2. Find the MCP section
3. Copy the MCP server link

Canonical public MCP endpoint: https://mcp.sendpulse.com/mcp

OpenAI-style quickstart

Use when the client supports adding a remote MCP server with custom headers.

1. Create a new MCP server connection in the client.
2. Paste the SendPulse MCP URL.
3. Set authentication to custom headers.
4. Add:

• X-SP-ID
• X-SP-SECRET

1. Copy ID and Secret from Account settings > API in SendPulse.
2. Connect.
3. Review the access request and approve it.

Cursor quickstart

1. Open Cursor Settings > MCP.
2. Add a custom MCP server.
3. Use config like:

{
  "mcpServers": {
    "sendpulse_mcp_service": {
      "url": "https://mcp.sendpulse.com/mcp"
    }
  }
}

1. Save the config.
2. Click Connect next to the server.
3. Complete the browser authorization flow when redirected.
4. Approve access.

First successful MCP action

Before doing writes:

1. Open the visible tool list in the client.
2. Cross-check against the official tools list page.
3. Optionally verify the raw MCP server path with scripts/mcp_handshake_test.py if you need protocol-level confirmation outside the UI.
4. If needed, execute a real read-only tool call with scripts/mcp_call_tool.py.
5. Run one harmless read-only request first.

Good first requests:

• Show me list of my bots
• Show my account info
• List available tools for my SendPulse account

Live raw MCP verification already confirmed these safe read-only paths:

• chatbots_account_show
• chatbots_bots_list

The SendPulse docs explicitly describe Show me list of my bots as a valid first example that maps to chatbots_bots_list.

Safety and execution guidance

• Approve only the tools needed for the current task.
• Prefer read-only verification before any write action.
• If several bots/subscribers have similar names, provide ID/username to disambiguate.
• If the client shows an error, check both authorization status and the visible logs.

What MCP is good for

Prefer MCP when the goal is conversational control of SendPulse features through an AI client, especially for:

• chatbot operations
• CRM actions
• account lookups
• campaign actions
• agent-driven workflows

Use direct REST API instead when you need backend-to-backend integrations, deterministic endpoint control, or SDK / webhook work.