SyncFlo MCP Server
The SyncFlo MCP (Model Context Protocol) server lets you connect MCP-compatible AI clients—such as Claude, Codex, and Cursor—directly to your SyncFlo account. Once connected, your AI assistant can read leads, conversations, campaigns, orders, catalogue, knowledge base resources, and analytics, and perform authorized actions like sending messages or creating campaigns.
Thin Protocol Adapter
The MCP server acts as a thin protocol adapter sitting on top of the existing SyncFlo REST API. It introduces no new authorization model: it reuses the existing sflo_live_ API keys, the existing scope system, rate limits, idempotency mechanism, and standard error envelope.
Connection Details
| Property | Value |
|---|---|
| Server URL | https://dashboard.syncflo.xyz/api/mcp |
| Transport | Streamable HTTP (JSON-RPC 2.0 over POST), stateless |
| Authentication | Authorization: Bearer sflo_live_... |
| Dashboard Page | Developer Tools → MCP Connect (/dashboard/mcp) |
| Availability | Eligible plans only (Growth / Custom tiers) |
* A connection is authenticated solely by the Bearer API key. The account, owner, and effective permissions are derived only from the key—never from any client-supplied parameter.
How to Connect
Create an API Key
Go to Developer Tools → API Docs in your dashboard. Create a new key and choose your scopes. (We recommend the read-only preset for safe, analysis-only access).
Configure your Client
Register the SyncFlo remote MCP server in your AI client using the server URL and your API key as a Bearer token.
Use SyncFlo Tools
Your AI client will automatically discover the tools permitted by your key's scopes and make them available in chat sessions.
Client Configuration
{
"mcpServers": {
"syncflo": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://dashboard.syncflo.xyz/api/mcp",
"--header", "Authorization: Bearer sflo_live_YOUR_KEY"]
}
}
}Note: Claude.ai also supports adding a custom connector by URL with a Bearer header.