Setell-AI/setell-mcp

Drive your Setell quote-to-cash workflow from any MCP-aware agent — Claude Code, Claude.ai, ChatGPT, or any client that speaks the Model Context Protocol.
Setell is a vertical agent for small-business quote-to-cash (machine shops, contractors, HVAC, service businesses). It ingests inbound email, drafts AI quotes, applies structured revisions, sends invoices, and syncs to QuickBooks. Setell exposes the same agent across three peer surfaces: a web app, the Gmail inbox, and any MCP-aware agent. @setell/mcp is the third surface — it lets you ask "what's stale?", "show me the Cooper job", or "draft a follow-up" from whatever agent you live in, without leaving it. Built for operators who run their business from Claude Code, and for bookkeepers and fractional CFOs who drive Setell on behalf of an operator.
> **Status:** Published on npm as @setell/mcp (0.7.x) — Pro-tier feature. A 25-tool surface: 16 read-only + 9 mutating (compose, send, schedule, select-tier, save-customer-memory, set-autonomy, update-shop-profile). Two transports: local stdio (npx -y @setell/mcp) and the hosted remote connector (https://go.setell.ai/api/mcp). See docs/BET-3-SETELL-MCP-V0.md in the main repo for the full design.
Requires
- A Setell account. The Free tier covers read-only exploration; the **Pro** tier is required to use the agent channel end-to-end (the boot health probe fails closed with an upgrade link if your plan doesn't qualify).
- Node.js 18 or newer.
- An MCP-aware client. Tested with Claude Code, Claude desktop, and the Claude.ai Custom Connector flow.
Install
The server is published to npm as @setell/mcp. Most clients run it via npx so you don't have to install anything globally.
If you do want a global install:
Configure
You need a **Setell extension key**. Mint one in your Setell account at **Settings → Extension Key** (go.setell.ai/settings). The page shows the raw key exactly once — copy it into your MCP client config below. The key is per-user, revocable from the same page, and resolves directly to your Setell tenant. The same key powers the Chrome extension.
Claude Code
Or edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) / %APPDATA%\Claude\claude_desktop_config.json (Windows) directly:
Restart Claude Code (or the desktop app). The Setell tools, resources, and prompts will appear in the server-status panel.
Remote endpoint (no local install)
Setell also hosts the same 25-tool surface as a remote MCP server — no Node, no npx, nothing local:
Any client that supports remote MCP servers with custom headers (Claude Code, Claude Desktop, API integrations) can use it today. Auth, plan gating, and tenant scoping are identical to the stdio path — same key, same backend.
Claude.ai (Custom Connector)
Claude.ai's web Custom Connector connects to the hosted endpoint above (https://go.setell.ai/api/mcp) with a browser sign-in — no local install and no manual key. Prefer a local server? Claude.ai Desktop can also run the stdio npx -y @setell/mcp invocation via the config above.
ChatGPT desktop and other MCP clients
Any client that supports stdio MCP servers can use the npx -y @setell/mcp invocation above. Set SETELL_EXTENSION_KEY in the client's per-server environment.
Environment variables
| Variable | Required | Default | Notes |
| ---------------------- | -------- | ----------------------- | -------------------------------------------------------------------------------------- |
| SETELL_EXTENSION_KEY | Yes | — | Per-user bearer key minted at go.setell.ai/settings. |
| SETELL_API_URL | No | https://go.setell.ai | Override for staging / local dev. No trailing slash. |
How auth works
The MCP server reads SETELL_EXTENSION_KEY at boot, calls /api/mcp/v1/health once to verify the key, plan, and integrations, and then attaches the key to every backend request as Authorization: Bearer . The Setell backend re-resolves the key on every request — the MCP process never holds tenant data and never opens a database connection.
If the key is missing, malformed, revoked, or your plan doesn't qualify, the MCP server exits with a clear error message before any tool registers. The error surfaces in your MCP client's server-status panel rather than as a hung connection.
See docs/BET-3-SETELL-MCP-V0.md §4 for the full auth model.
What's in it
The surface is intentionally tight — a small, discoverable set that we expand as we watch how external agents actually use it.