뒤로 가기

Astell MCP

How Astell shows up inside Claude, ChatGPT, Cursor, and other MCP-ready assistants, how to connect it, and what it costs.

What is Astell MCP?

Astell publishes an MCP connector (Model Context Protocol), so you can plug Astell into any assistant that supports MCP with OAuth, such as Claude, ChatGPT, and Cursor, with no API keys to manage. Search and act on your workspace from the tools your team already uses. ChatGPT support depends on your OpenAI plan and OpenAI's MCP rollout.

How does Astell show up inside my assistant?

Connect Astell via MCP (OAuth, no API keys) and the assistant can query your Astell workspace directly: loops, artifacts, people, and citations, all permission-aware. Astell's job in that setup is context. If you then ask the assistant to act (update the ticket, send the email), the action runs through that assistant's own connectors for those tools, not through Astell Actions. The difference Astell makes is that the assistant acts on grounded, pre-ingested company data instead of whatever its connectors can fetch live, which means fewer wrong guesses and better drafts.

How do I connect an assistant?

Open Workspace settings → Connectors and copy the MCP URL. Add it as a custom MCP connector in your assistant: in Claude that is Settings → Connectors → Add connector; other clients have an MCP or connectors section in their settings. Sign in once in your browser and choose which Astell workspaces the connection may access. The same page lists every connection you have authorized, so you can change its workspaces or revoke it at any time.

Which plans include MCP connectors?

MCP connectors are available on all plans:

• Sapling: available, but throttled
• Tree: available, unlimited
• Grove: available, unlimited
• Forest (Enterprise): available, unlimited

Is MCP connector usage limited?

MCP connector usage is unlimited on Tree and above, subject to the Fair Use Policy. Sapling includes additional throttling to keep free-tier usage reliable for everyone.

Does MCP connector usage consume tokens?

When you use Astell through MCP inside another assistant, that assistant runs its own model, so the response itself isn't billed against your Astell token pool. Astell's role is supplying context: retrieving from your synced workspace (free) and, if a query pulls in new Processed Data, ingesting it at the normal token rate. Actions taken from inside that assistant run through its own connectors, so they aren't billed as Astell Actions either.

How do I get started?

Connect Astell from your assistant's connector settings and authorize via OAuth; there are no API keys to manage. MCP connectors are a feature of every Astell plan, not a separate subscription. On Sapling, MCP is available but throttled; Tree ($20/seat/month annual, $25 monthly) and above include unlimited MCP along with the Exacto model and expanded memory. (Astell agents are available on Tree and above too, but each agent is its own paid seat.)

Can Astell use my other tools' MCP servers?

Yes, that is the other direction. Link GitHub, Linear, Slack, Gmail, Google Drive, Google Calendar, or Notion to a workspace and Astell chat can call their MCP servers, with an approval card before every call; each integration card under Workspace settings → Integrations can pause and resume them. See MCP servers in Astell chat.