Hosted connector (Claude, ChatGPT and other AI assistants)

Connect your workspace to an AI assistant in a few clicks. The hosted server at https://app.sellinger.ai/api/v2/mcp speaks the streamable HTTP MCP transport with OAuth sign in, so there is nothing to install and nothing to run locally.

Set up in claude.ai

1. In claude.ai, open Settings, then Connectors.
2. Click Add custom connector and paste https://app.sellinger.ai/api/v2/mcp as the URL. No client ID or secret is needed.
3. Click Connect. You are sent to Sellinger to sign in.
4. Pick a workspace and an access level, then approve. Claude returns you to the connector list, connected.

Access levels

You choose the access level when you connect, and can reconnect later to change it.

• Full access. Read and act: send messages, update leads, approve outreach, import prospects.
• Read only. List and read everything, with no sends, no writes and no approvals.

27 tools

Grouped by category. Read only tools are marked; everything else can change data or send a message.

Saved prompts

Four one-click workflows that chain the tools above. Clients that render MCP prompts (claude.ai) offer these directly.

• weekly_pipeline_review (Weekly pipeline review). Pull this week's pipeline health, meetings and approvals, then summarize wins, risks and next actions.
• prep_my_day (Prep my day). Brief today's meetings, surface hot leads, and summarize pending approvals as decisions to make.
• find_new_prospects (Find new prospects). Translate an ICP description into a search_people query, present candidates, then import only with explicit confirmation.
• audit_stale_leads (Audit stale leads). Spot check the oldest ENGAGED and MEETING leads, classify each, and propose next steps without acting.

Limits

• Tool outputs are compacted for token efficiency: long fields are truncated, lists are capped at 100 rows, and heavy per-lead fields (company analysis, deep research, profile data) are omitted from list views. Call get_lead for the full record.
• Each tool call has a 300 second maximum runtime.
• Access tokens last 8 hours; the refresh token lasts 90 days, so reconnecting stays rare.

Team MCP REST API

For direct HTTP access instead of the hosted connector: 167+ team-scoped REST endpoints for agents, leads, pipeline, analytics, and integrations. Designed for backend automations and custom CRM sync, using an API key rather than OAuth.

• All responses are JSON. Use HTTPS only.
• Data is scoped to the team in x-team-id.
• SMS is not available via send-message on MCP routes.
• Leads with status SUGGESTED or DISCARDED are excluded from list/count endpoints.

Authentication

Create an API key under Integrations → API. Every MCP request needs your key and team ID.

# Required headers for API key access
curl "https://app.sellinger.ai/api/v2/mcp/agents" \
  -H "Authorization: Bearer sk_live_your_api_key" \
  -H "x-team-id: your-team-uuid"

# Also supported:
#   X-API-Key: sk_live_...
#   X-Sellinger-API-Key: sk_live_...

Agents

curl "https://app.sellinger.ai/api/v2/mcp/agents" \
  -H "Authorization: Bearer sk_live_your_api_key" \
  -H "x-team-id: your-team-uuid"

Example response shape:

{
  "agents": [
    {
      "id": "uuid",
      "name": "Outreach",
      "agent_type": "outbound",
      "is_active": true,
      "persona_id": "uuid",
      "channel_counts": { "linkedin": 1, "email": 1 }
    }
  ],
  "count": 4
}

Leads

List with filters, create via POST, update with PATCH. At least one of email, phone, or LinkedIn URL is required when creating.

# List NEW leads
curl "https://app.sellinger.ai/api/v2/mcp/leads?status=NEW&limit=25&offset=0" \
  -H "Authorization: Bearer sk_live_your_api_key" \
  -H "x-team-id: your-team-uuid"

# Create a lead
curl -X POST "https://app.sellinger.ai/api/v2/mcp/leads" \
  -H "Authorization: Bearer sk_live_your_api_key" \
  -H "x-team-id: your-team-uuid" \
  -H "Content-Type: application/json" \
  -d '{
    "full_name": "Jane Doe",
    "email": "jane@company.com",
    "lead_source": "API",
    "primary_channel": "email",
    "agent_id": "optional-agent-uuid"
  }'

Query params for GET: status, stage, agent_id, channel, query, limit (max 100), offset.

Endpoint catalog

Paths are relative to /api/v2/mcp. Replace [id] with a UUID.

Self-host: Node MCP server (legacy)

Most people should use the hosted connector above. The mcp-server/ package remains available as a self-host option: it runs locally over stdio and exposes 15 high-level MCP tools that call this REST API. Use it if you want to run the server yourself rather than connect through the hosted OAuth endpoint. Install from the repo, build, then configure your client:

cd mcp-server
npm install
npm run build

Environment variables:

SELLINGER_API_KEY=sk_live_...
SELLINGER_TEAM_ID=your-team-uuid
SELLINGER_BASE_URL=https://app.sellinger.ai   # optional, default production

Claude Desktop or Cursor stdio config (replace the path with your checkout):

{
  "mcpServers": {
    "sellinger": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-server/dist/index.js"],
      "env": {
        "SELLINGER_API_KEY": "sk_live_your_key_here",
        "SELLINGER_TEAM_ID": "your-team-uuid",
        "SELLINGER_BASE_URL": "https://app.sellinger.ai"
      }
    }
  }
}

Stdio tools include list_leads, send_message, list_agents, pipeline counts, hot leads, and more. The REST API exposes 167+ additional endpoints for direct HTTP access. See mcp-server/README.md in the repo.