The marketplace
Finding a module worth adding, and reading its page before you do.
The marketplace at odel.app/market holds three quite different things: modules Odel hosts, MCP servers it merely knows about, and gateways an organization has published. All three are listed the same way, and the label on each card says which is which.
Narrowing it down
The catalogue is large, so the filters matter more than the search box.
| Control | What it does |
|---|---|
| Search | Matches names, ids, taglines, tags, tool names, and the repository or registry name — not the full description |
| Tags | Search the tags, then keep one or leave it out. With more than one kept, choose whether a module must match any of them or all |
| Runs on | Odel, Odel Gateway, or Publisher's servers — see module types |
| Access | Remote or Local. Either one narrows to external servers: reachable over the network, or a package you run yourself |
| Sort | Most stars (the default), Recently updated, or Name. While you search, Best match is added and is the default |
What you've already added has a page of its own, My modules in the navigation. It shows whether each one is ready, with anything that needs action from you under Needs you.
The Local chip is worth knowing about. A local external server is distributed as a package that runs on your own machine, so there's nothing for Odel to put a URL in front of. Those listings are reference material, not something to connect.
Reading a module's page
A module page is one scrolling page with a section bar along the top. It opens on Overview — what it does and who owns it — and the Requirements section says how the module runs, how you sign in, and which credentials it asks for. Read that list before anything else. It's the clearest statement of what you'd be handing over.
Most modules also have a Tools section, listing the tools the server was found to expose. An external server with no address to reach — a package you run yourself — shows Install instead, because there was nothing to probe. A gateway has no Tools section: its tools sit behind its own door, so there's nothing to list here. Once you've added a module, a Your URL section appears and a Config link at the end of the bar leads to changing its credentials or removing it.
When the owner has more than one public listing, their name links to everything else they've published, which is usually the fastest way to judge whether a module is a one-off or part of someone's ongoing work. When this is their only listing, the name is plain text, and hovering it says so.
There are no reviews
Odel has no reviews or install counts to lean on. A module with a linked GitHub repo shows its star count, which you can also sort by, but for everything else judge a module by what it exposes, who owns it, and whether the credentials it wants match what it claims to do.
Adding one
The button is the same for everything you can add: Add to My modules, or Sign in to install when you're signed out. A gateway's own visibility decides whether you can add it; an external server can be added by anyone who can see the listing. Either way the address to point a client at appears once it's added. An external server also gets a second button beside the first, but only while you're acting as an organization you manage: Add to that organization, which opens the developer portal to set the server up as a draft gateway for it, to finish and publish there, rather than installing it for you. Default modules have no button — they're platform pieces, listed for visibility only.
Installing
Adding a module, and giving it credentials.
Module types
What the label on each card means.
Gateways and installing
Adding a server for yourself, or adopting it as an organization's gateway.
Connecting a client
Getting your modules into Claude, Cursor, or ChatGPT.
The vault
Store a key once and reuse it everywhere.