Docs / Setell for agents (MCP)

Connect from Claude / ChatGPT / Claude Code

Pro

Overview

Setell is a remote MCP connector. Point your agent at one URL, approve the connection on a Setell consent screen, and Setell's tools show up inside Claude, ChatGPT, or Claude Code:

https://go.setell.ai/api/mcp

No key to copy, nothing to install, no Node.js. Sign-in and consent happen in your browser, and you can disconnect any agent at any time from Settings → Connected agents.

This is a Pro feature. You can connect on any plan, but day-to-day use needs Pro. If your plan doesn't qualify, calls stop with a clear message and an upgrade link — nothing breaks quietly.

Connect from Claude (claude.ai)

1. In Claude, open Settings → Connectors and choose Add custom connector.

2. Paste the connector URL:

https://go.setell.ai/api/mcp

3. Claude sends you to Setell's consent screen. Sign in if you aren't already, review what the connection can do, and click Connect.

4. You land back in Claude with Setell's tools live. Try: "Use the Setell morning brief" or "Find my stale jobs."

Connect from Claude Code

One line in your terminal:

claude mcp add --transport http setell https://go.setell.ai/api/mcp

Then run /mcp inside Claude Code and pick setell to sign in — the same browser consent screen opens, and the tools light up when you approve.

Connect from ChatGPT

In Settings → Connectors, add a custom connector with the same URL (OpenAI may require developer mode for custom connectors on your plan). ChatGPT walks you through the same Setell sign-in and consent.

Managing connected agents

Every agent you approve appears in Setell → Settings → Connected agents with when it connected and when it was last used. Disconnect revokes its access immediately — the agent simply stops working until you reconnect it from the client. Approving the same client again later creates a fresh connection.

The key-based alternative

Prefer a credential you manage yourself, or using an MCP client that can't open a browser? Two options, both powered by the same key:

  • Hosted, with a key: point your client at https://go.setell.ai/api/mcp with an Authorization: Bearer setell_ext_... header.
  • Local (stdio): run npx -y @setell/mcp with SETELL_EXTENSION_KEY=setell_ext_... in the server's env. Needs Node.js 18+.

Mint the key in Settings → Chrome Extension API Key (one key powers the Chrome extension and MCP; it's shown once — Rotate replaces it everywhere).

What the connection can do

A connected agent has the same reach as the Setell app, under your rules: read jobs, customers, and quotes; draft, send, and schedule quotes; save customer notes and pricing memory. Sends still honor your autonomy mode — if you review sends in the app, agent-initiated sends wait for the same review.

Troubleshooting

  • The consent screen says "Can't start this connection." The connector handshake went stale. Remove the connector in your agent and add it again with the URL above.
  • "Setell could not authenticate this access token." The connection was disconnected or expired. Reconnect from your agent (Claude refreshes automatically; a fully revoked connection needs a fresh approve).
  • "Setell-MCP requires the Pro plan." Your plan doesn't qualify. Upgrade at Settings → Billing — the existing connection starts working immediately, no reconnect needed.
  • Key-based setup says it needs SETELL_EXTENSION_KEY. The key didn't reach the server — set it inside your agent's config (under the server's env), not just in your terminal.
  • Still stuck → docs/reference/troubleshooting.

FAQ

  • Do I have to install anything? Not for the browser flow — it's a hosted connector. Only the local stdio option needs Node.js.
  • Where does my data go? Your agent talks directly to Setell over HTTPS. The agent never stores your account credentials; every request is checked against Setell, and consent is scoped to your account only.
  • Can my bookkeeper connect? Yes — they connect from their own agent and approve with the Setell account they work in. Each connection is listed (and revocable) in that account's Settings.
  • What's the difference between disconnecting in Setell vs removing the connector in Claude? Same end result. Disconnecting in Setell revokes the tokens server-side instantly; removing in Claude also tells Setell to revoke. Use Setell's Settings when you want to be certain access is gone.
  • Is the consent screen asking for my whole account? It grants the MCP toolset for your account — the same scope as an extension key, but expiring, per-client, and revocable from Settings.

Related

docs/mcp/what-is-setell-mcp · docs/mcp/capabilities · docs/account/keys · docs/account/upgrade-billing

Ready to try it on your own quotes?

Start free — no credit card. 14 days of unlimited Pro, then 3 free quotes a month.

← All docs