Can I host my own MCP server and still use Helix?
Yes. A vanilla MCP server can call the Helix REST API or proxy a subset of Helix tools. Helix and your MCP server are not mutually exclusive.
Compare
Helix vs A vanilla MCP server
Anyone can stand up an MCP server. Helix is what you get when the MCP server is wrapped in an identity layer — a real mailbox, scoped permissions, an audit log, and a human-approval queue that survive across LLM clients and sessions.
The Model Context Protocol is an open standard for letting LLMs call typed tools — anyone can host an MCP server. A vanilla MCP server site
Feature-by-feature
| Feature | Helix | A vanilla MCP server |
|---|---|---|
| What ships | Identity, mailbox, calendar, approvals, audit log | Just the MCP transport + your tools |
| Email integration | Gmail, Outlook, agent inbox, all preconfigured | You wire it (Nylas, raw IMAP, etc.) |
| Approvals | Per-identity policy, queue UI, audit log | You build it |
| Auth | PASETO v3 cookies via dashboard SSO | You pick — JWT, OAuth, mTLS, etc. |
| Hosting | Managed (Cloudflare Workers + D1) | You host |
| Free tier | Free, no credit card | Whatever your hosting bill is |
In plain prose
A vanilla MCP server is a transport. You get a protocol for typed tool calls — and the responsibility for everything else. Identity, scopes, persistence, hosting, mailbox plumbing, audit, and the human-approval UX are all yours to build.
Helix is the opinionated bundle. Each agent has a sponsor, a real mailbox, scoped permissions, an action log, and an approval policy. The MCP endpoint is one of several ways to drive it (the dashboard, REST API, and webhooks are the others).
If you only need a couple of bespoke tools wired to an LLM, a vanilla MCP server is fine. If you need an agent that sends email on someone’s behalf with audit and approval, Helix saves you months.
FAQ
Do I have to use the Helix MCP endpoint?
No. Helix exposes a REST API and webhooks alongside the MCP endpoint. The MCP endpoint is the easiest way to drive Helix from Claude, Cursor, ChatGPT, or n8n.
Where does the @nylas/helix-mcp-server package fit?
`@nylas/helix-mcp-server` is the open-source MCP shim that points at your Helix identity. You can vendor or fork it; the source is on GitHub under MIT.
Next step
Try the workflow this comparison points at: Helix for developers — MCP quickstart. Free, no credit card.
Newsletter
Want a heads-up when this comparison updates?
We update these matrices when either side ships something material.
No spam. Unsubscribe in one click.