MCP · the paid wire layer
The protocol is free. MCP is what we charge for.
Eternity itself is two plain-English files — write them anywhere with any AI, forever, for nothing. The hosted MCP server is the one place we sit between your AI client and inference compute, so it's the one thing we have to charge for.
✓ Free forever
- — writing intent.ety + implement.ety
- — using the protocol in any project
- — self-hosting your own MCP server
- — training models on the spec
$ Paid
- — our managed MCP endpoint
- — drop-in for Claude Desktop, Cursor, MCP clients
- — we pay the AI tokens, you pay us
- — priority routing + uptime
hosted MCP · pay only for what you call
Sign in to get your MCP endpoint.
No subscription. No monthly minimum. You sign in once, get a private endpoint and bearer token, and your bill grows only when an MCP call runs — typically fractions of a cent each. Set a notification threshold; we email you the moment usage crosses it.
How the hosted MCP works
- You point your MCP client at our endpoint. Claude Desktop, Cursor, or anything else that speaks MCP — same JSON-RPC.
- The MCP exposes the protocol's two-file flow: you send a directive, you get back an intent.ety + implement.ety pair, you approve, the build runs.
- We meter compute, not the protocol. The files themselves are still free — what's billed is the AI inference and orchestration we run on your behalf.
- You can leave any time. Your intent files are portable. Take them to a self-hosted MCP, another vendor, or no MCP at all — the protocol works without us.