1# SendPulse MCP Quickstart
2 
3Use this file when the task is specifically about connecting SendPulse MCP in a client and reaching the first successful tool call.
4 
5## Official source of truth
6 
7- MCP setup guide: `https://sendpulse.com/knowledge-base/account-settings/mcp-server`
8- MCP tools list: `https://sendpulse.com/knowledge-base/account-settings/mcp-tools`
9- MCP product page: `https://sendpulse.com/features/mcp`
10 
11## Before setup
12 
13Decide which client you are targeting:
14 
15- OpenAI / ChatGPT-style MCP client
16- Cursor
17- another MCP client
18 
19Do not assume the auth flow is identical across clients.
20 
21## Get the MCP link
22 
23In SendPulse:
24 
251. Open `Account settings > API`
262. Find the MCP section
273. Copy the MCP server link
28 
29Canonical public MCP endpoint:
30`https://mcp.sendpulse.com/mcp`
31 
32## OpenAI-style quickstart
33 
34Use when the client supports adding a remote MCP server with custom headers.
35 
361. Create a new MCP server connection in the client.
372. Paste the SendPulse MCP URL.
383. Set authentication to custom headers.
394. Add:
40   - `X-SP-ID`
41   - `X-SP-SECRET`
425. Copy ID and Secret from `Account settings > API` in SendPulse.
436. Connect.
447. Review the access request and approve it.
45 
46## Cursor quickstart
47 
481. Open `Cursor Settings > MCP`.
492. Add a custom MCP server.
503. Use config like:
51 
52```json
53{
54  "mcpServers": {
55    "sendpulse_mcp_service": {
56      "url": "https://mcp.sendpulse.com/mcp"
57    }
58  }
59}
60```
61 
624. Save the config.
635. Click Connect next to the server.
646. Complete the browser authorization flow when redirected.
657. Approve access.
66 
67## First successful MCP action
68 
69Before doing writes:
70 
711. Open the visible tool list in the client.
722. Cross-check against the official tools list page.
733. Optionally verify the raw MCP server path with `scripts/mcp_handshake_test.py` if you need protocol-level confirmation outside the UI.
744. If needed, execute a real read-only tool call with `scripts/mcp_call_tool.py`.
755. Run one harmless read-only request first.
76 
77Good first requests:
78 
79- `Show me list of my bots`
80- `Show my account info`
81- `List available tools for my SendPulse account`
82 
83Live raw MCP verification already confirmed these safe read-only paths:
84 
85- `chatbots_account_show`
86- `chatbots_bots_list`
87 
88The SendPulse docs explicitly describe `Show me list of my bots` as a valid first example that maps to `chatbots_bots_list`.
89 
90## Safety and execution guidance
91 
92- Approve only the tools needed for the current task.
93- Prefer read-only verification before any write action.
94- If several bots/subscribers have similar names, provide ID/username to disambiguate.
95- If the client shows an error, check both authorization status and the visible logs.
96 
97## What MCP is good for
98 
99Prefer MCP when the goal is conversational control of SendPulse features through an AI client, especially for:
100 
101- chatbot operations
102- CRM actions
103- account lookups
104- campaign actions
105- agent-driven workflows
106 
107Use direct REST API instead when you need backend-to-backend integrations, deterministic endpoint control, or SDK / webhook work.
108