Building on Odel
Ship a module Odel hosts, put your own server behind an Odel URL, or run a gateway for your team.
Writing an MCP server is the easy part. What takes the time is everything around it — deciding how callers authenticate, keeping their credentials somewhere defensible, hosting the thing, and then getting it in front of anyone.
That's the part Odel takes. You write the tools; the sign-in, the secret handling, the runtime, and the listing come with the platform.
What you can ship
A module Odel hosts. You write TypeScript, connect a GitHub repository, and the developer
portal builds and deploys it. It runs in an isolate on Odel's edge, reachable at
mcp.odel.app/@you/your-module. Nothing to operate.
A module on your own backend. The code runs on your infrastructure and Odel fronts it — same URL shape, same sign-in, same marketplace listing. Use this when the work can't move: it needs a database you already run, a GPU, or a network only you can reach.
A gateway. A proxy your organization shares: one URL for a server Odel doesn't run. Some upstreams take a single credential the organization holds. One with its own per-person sign-in needs an OAuth app: Odel registers one itself where the upstream allows that, and otherwise you register it once. Either way, everyone who uses the gateway signs in to the upstream themselves. Gateways are managed in the developer portal.
What comes with the platform
| Concern | How it's handled |
|---|---|
| Authentication | Odel is an OAuth 2.1 server. Clients register themselves, so you never issue or distribute credentials. |
| Secrets | A user's API keys are stored in the vault and injected at call time. Your code receives a value and learns nothing about where it came from. |
| Hosting | Hosted modules run in a V8 isolate per call. No server, no scaling to think about. |
| Distribution | Publishing lists you in the marketplace, where the connect flow is one click. |
Where to start
Creating modules
Write your first module and run it locally.
Module SDK
Tools, context, errors, and response schemas.
Developer portal
Projects, deployments, secrets, and publishing.
MCP Inspector
Call any MCP server and read the raw traffic.
How the vault works
Addresses, encryption, references, audit.
Architecture
What runs where, and how a call reaches your code.