Ce guide n’est pas encore disponible en français : vous lisez la version originale en anglais.
Parcourir la documentation
API et agents IA
Connect your AI agent (MCP)
3 min de lecture · Mis à jour le
Sendtim runs a remote Model Context Protocol (MCP) server. Connect the AI agent you already use and ask for what you need: “draft a welcome series for new signups”, “which campaign had the best click rate this month?”. Your AI provider does the reasoning and bills its own usage; Sendtim provides secure access to your workspace, with no AI credits on any plan. The agent acts as you, sees only the workspaces you belong to, and can do only what your role allows.
Server URL
https://sendtim.com/api/mcpAdd it as a remote Streamable HTTP server. The first time you connect, a browser window opens so you can sign in to Sendtim and approve access. Signed in, Settings → AI agents shows the same instructions and recent agent activity.
ChatGPT
- In ChatGPT, open Settings → Apps & Connectors and turn on Developer mode under Advanced settings.
- Choose Create, name it Sendtim and paste the server URL
https://sendtim.com/api/mcp. Leave authentication on OAuth. - Sign in to Sendtim in the window that opens and approve access.
- In a new chat, enable the Sendtim connector from the tools menu.
Custom connectors depend on your ChatGPT plan and workspace settings. If you do not see Developer mode, your plan or admin has not enabled it.
Claude
- Open Settings → Connectors and choose Add custom connector.
- Name it Sendtim, paste
https://sendtim.com/api/mcpand select Add. - Select Connect, sign in to Sendtim and approve access.
Claude Code
- Run the command below.
- Inside Claude Code, run
/mcp, choose sendtim and sign in through your browser.
claude mcp add --transport http --scope user sendtim https://sendtim.com/api/mcpCodex
- Add the server, then sign in:
codex mcp add sendtim --url https://sendtim.com/api/mcp
codex mcp login sendtimPrefer config files? Add [mcp_servers.sendtim] with url = "https://sendtim.com/api/mcp" to ~/.codex/config.toml, then run codex mcp login sendtim.
Cursor
- Open Cursor Settings → MCP and add a new server, or edit
~/.cursor/mcp.jsondirectly: - Cursor shows Needs login next to the server; select it and sign in to Sendtim.
{
"mcpServers": {
"sendtim": { "url": "https://sendtim.com/api/mcp" }
}
}Other MCP clients
- Add
https://sendtim.com/api/mcpas a remote Streamable HTTP server. - Clients that support OAuth (Client ID Metadata Documents or dynamic client registration) open a Sendtim sign-in on first use; nothing else is needed.
- A client without OAuth can send a workspace API key from Settings → API as an
Authorization: Bearerheader instead. A key reaches only its own workspace.
What it can do
| Area | Operations |
|---|---|
| Contacts | Search, view activity, create, update, suppress, delete. |
| Lists and segments | Create, edit, preview how many contacts a rule matches, manage members. |
| Campaigns | Create, write the email from simple copy or HTML, send a test, schedule, send, pause, resume, cancel, read reports. |
| Automations | Create, edit triggers and steps, activate or pause, enroll a contact, read performance. |
| Templates | Create from simple copy or HTML, view, update, duplicate, delete. |
| Forms | List with conversion rates, read submissions. |
| Analytics | Workspace overview, audience growth, engagement, top campaigns. |
Context and ready-made workflows
Agents can read MCP resources before they act: sendtim://workspace/current (plan, sender, lists, segments and merge tags) and sendtim://docs/campaigns, …/automations, …/merge-tags, …/audiences and …/deliverability, which are these guides.
MCP prompts start common jobs: create_welcome_series, create_reengagement_flow, create_product_launch_campaign and analyze_campaign_performance. They guide your agent step by step and leave sends and activations for you to approve.
Safety
- Anything that emails people, schedules a send, activates an automation or deletes data comes back as a preview first. Your agent has to show it to you and get your go-ahead before it runs.
- Sending a campaign needs the admin role, exactly as in the dashboard.
- Every change is recorded in the workspace audit log, marked as made through MCP.
- Removing someone from a workspace ends their agent’s access to it immediately.
Workspace settings, billing and CSV imports stay in the dashboard.
À lire aussi dans API et agents IA
- API et agents IA
Connect PrestaShop to Send Tim
Download the free PrestaShop module, connect your workspace, import opted-in customers, and configure abandoned-cart automation.
- API et agents IA
Connect Clay to Sendtim
Send enriched Clay contacts to Sendtim, import Sendtim contacts into Clay, and start an automation from a Clay row.
- API et agents IA
Use the Sendtim REST API
Authenticate with an API key and manage contacts, lists, campaigns and automations from your own code.
- API et agents IA
Connect Sendtim to Zapier
Add contacts from the other tools you use, and let a new contact, an unsubscribe or a finished campaign start work elsewhere.
