Selda MCP

Connect an AI client to a Selda workspace.

Others sell you a tool. Selda builds your sales machine: it watches for the moment worth reaching out, researches each company, writes the message in your customer's language, sends it from your own inbox and brings the reply back to you. A person approves every send. This repository is the machine readable documentation for driving that engine from outside the app, over the Model Context Protocol or plain HTTP.

MCP and the API are on every plan, the free one included. There is no tier to reach before you can connect a client — see Keys, scopes and isolation for what a key on a free workspace can do.

The narrative documentation lives at docs.selda.ai/reference/mcp. When the two disagree, the live capability manifest described below is right.

What you can do with it

What you cannot do with it, on purpose

Nothing here sends outreach. A script can build a campaign all the way up to drafted messages. A human presses send, in the Selda app. There is no function that launches a campaign's sends, and there is no flag that turns that off.

This is not a limitation we plan to remove. It is the product's central claim: Selda recommends, the human decides.

Connect

OAuth, recommended for Claude.ai, ChatGPT and Cursor

Add this as a custom connector:

https://mcp.selda.ai/api/mcp

The server advertises OAuth, so the client walks you through logging in and picking a workspace. Nothing to paste.

A static key, for Claude Code, scripts and CI

Create a key in the Selda app under Settings → Connections → MCP server. The full key is shown once.

claude mcp add --transport http selda https://mcp.selda.ai/api/mcp \
  --header "Authorization: Bearer $SELDA_API_KEY"

Any other MCP client that reads a config file takes the same URL and the same header.

Keys, scopes and isolation

A key is sk_live_… (live) or sk_test_… (sandbox). Only a SHA-256 hash of it is ever stored, so a lost key is revoked, never recovered.

Every call is bound to the organization that owns the key. The org id is injected server side from the validated key and an orgId in your request body is ignored. One organization's key cannot reach another organization's data.

Every plan can connect, the free one included. Creating a key is not gated on a tier or an invoice. A workspace standing in test mode always mints sk_test_; a workspace approved for live always mints sk_live_. The prefix states the environment and grants nothing on its own — every gate reads the stored environment and the

... View full README on GitHub