Which servers are supported in v1?

GitHub (code, issues, pull requests), Firecrawl (web scraping and crawling), and Context7 (live library documentation). Each represents a different shape of integration: code host, web fetcher, reference index.

On which plan are external MCP servers available?

Max. The MCP client surface is part of the Max plan capabilities.

Can I add my own MCP server?

Not in v1. The whitelist exists to remove supply chain risk, which is the most common attack surface in MCP integrations. We are tracking demand and will expand the list one server at a time after review.

Where do I configure them?

Settings → Integrations → MCP servers inside Alma. Pick a server, paste the token if it needs one, and the tools appear in chat the moment the connection is live.

External MCP servers

Alma can read from a curated whitelist of external MCP servers — GitHub, Firecrawl and Context7 in v1 — and use their tools inside chat. The model picks tools per turn; results arrive as inline citations. Read-only on purpose: external servers feed Alma context, they never write into your account. Available on Max.

MCP is the open Model Context Protocol from Anthropic. Alma plays the client side: it discovers the tools an external server exposes, surfaces them in the model tool palette, and forwards calls with your stored credentials. Whitelist v1 includes GitHub (search code, read files, list issues, read pull requests), Firecrawl (scrape and crawl any web page) and Context7 (live library documentation lookups).

Three guarantees: read-only (Alma never invokes write tools), per-user encrypted credentials (tokens never shared between users), allow-listed servers only (no Add any URL field). Custom servers and write tools are intentionally not in v1.

See plans