What is MCP (Model Context Protocol)?

MCP is an open standard that lets AI assistants discover and call external tools. Sellinger provides a local stdio MCP server (mcp-server/) that connects Claude Desktop, Cursor, and other MCP clients to your CRM data via our REST API.

Which AI clients are compatible?

Claude Desktop and Cursor work today via the local stdio mcp-server package. Any MCP-compatible client that supports stdio transport can use the same setup. There is no hosted remote MCP URL — install the server from the repo and configure your client with a command, not a web address.

What tools does Sellinger expose?

The stdio mcp-server package exposes ~13 high-level MCP tools (list_leads, send_message, list_agents, pipeline counts, and more). For direct HTTP access, the Team REST API provides 165+ endpoints under /api/v2/mcp for leads, campaigns, analytics, and integrations.

Is it read-only or read-write?

Both stdio MCP tools and REST endpoints support read and write operations where your API key permissions allow — query leads, send messages, update statuses, and manage pipeline data.

How is authentication handled?

Generate an API key from Settings → Integrations in the Sellinger app, plus your team UUID (x-team-id). Configure both in your stdio MCP client env vars or REST request headers. All requests are scoped to your workspace.

What are the rate limits?

REST API requests follow standard platform rate limits. Use response headers to handle throttling in automations. See the in-app API docs for current limits on your plan.

All communication uses HTTPS/TLS. API keys are scoped to your workspace and can be rotated from the dashboard. Data never leaves your team scope.

Can I restrict which tools my AI can access?

Use separate API keys for different automations and limit write operations in your workflows. Granular per-tool MCP key scopes are not available today — contact us for enterprise requirements.

MCP

Connect Your AIs to Sellinger

Connect Claude, Cursor, or custom agents to Sellinger via the local stdio MCP server or our Team REST API. Query leads, send messages, and automate workflows — with ~13 stdio MCP tools and 165+ REST endpoints.

View Setup Docs Book a Demo

13+ Stdio MCP Tools165+ REST EndpointsClaude & Cursor

See It In Action

Your AI Discovers and Uses Sellinger Tools

Install the local stdio MCP server or call the Team REST API directly. See setup examples below.

claude_desktop_config.json

// Local stdio MCP server (Claude / Cursor)
{
  "mcpServers": {
    "sellinger": {
      "command": "node",
      "args": ["/path/to/mcp-server/dist/index.js"],
      "env": {
        "SELLINGER_API_KEY": "sk_live_...",
        "SELLINGER_TEAM_ID": "your-team-uuid",
        "SELLINGER_BASE_URL": "https://your-app.sellinger.ai"
      }
    }
  }
}

What's Exposed

Full Access to Your Sales Intelligence

Leads, campaigns, conversations, and analytics via stdio MCP tools or direct REST endpoints.

Leads & Contacts

Read lead profiles, enrichment data, qualification status, and full conversation history across channels.

Campaigns

List, create, pause, and modify outreach campaigns. Full CRUD access to your campaign configuration.

Conversations

Access complete message threads across all channels — LinkedIn, Email, WhatsApp, SMS, Chat.

Analytics

Pipeline metrics, channel performance, conversion rates, and historical trends — all queryable.

Actions

Send messages, book meetings, update lead status, trigger workflows — full write access.

Configuration

Manage agent settings, channel configs, ICP definitions, and workspace preferences.

Who It's For

Built for Developers, Ops Teams, and AI Power Users

Whether you're building custom agents, integrating into your IDE, or automating workflows — MCP gives you full access.

Custom AI Agents

Build your own AI agents that leverage Sellinger's multi-channel infrastructure. Read data, take actions, orchestrate workflows.

Learn more

IDE Integration

Use Sellinger data directly in Cursor, VS Code, or any MCP-compatible IDE. Query leads while you code.

Learn more

Workflow Automation

Connect Sellinger to your AI-powered ops pipeline. Trigger actions based on external events.

Learn more

How It Works

Connect Any AI in 4 Steps

From API key to full integration in minutes. No SDK required — just standard MCP.

Get API Key

Generate an API key and copy your team UUID from the Sellinger dashboard.

Install MCP Server

Build mcp-server/ from the repo and add the stdio config to Claude or Cursor.

Discover Tools

Your AI discovers ~13 stdio tools (list_leads, send_message, and more).

Build & Execute

Query data, send messages, or call 165+ REST endpoints directly.

Get API Key

Generate an API key and copy your team UUID from the Sellinger dashboard.

Install MCP Server

Build mcp-server/ from the repo and add the stdio config to Claude or Cursor.

Discover Tools

Your AI discovers ~13 stdio tools (list_leads, send_message, and more).

Build & Execute

Query data, send messages, or call 165+ REST endpoints directly.

0+Stdio MCP Tools

0+REST Endpoints

0LocalStdio Server

0HTTPSREST API

Connect Your First AI to Sellinger

Follow the setup guide to install the stdio MCP server or use the REST API directly.

View Setup Docs Book a Demo

13+

Stdio Tools

165+

REST Routes

Claude & Cursor

Clients

FAQ

Frequently Asked Questions About MCP

Everything you need to know about connecting your AI tools to Sellinger via the Model Context Protocol.

// Local stdio MCP server (Claude / Cursor) { "mcpServers": { "sellinger": { "command": "node", "args": ["/path/to/mcp-server/dist/index.js"], "env": { "SELLINGER_API_KEY": "sk_live_...", "SELLINGER_TEAM_ID": "your-team-uuid", "SELLINGER_BASE_URL": "https://your-app.sellinger.ai" } } } }