Open source, Model Context Protocol
The connective tissue between AI and the tools it works in.
efaimo builds open MCP servers, plus the routing, auth, and discovery layer around them, so any model, Claude included, can reach any tool through one interoperable standard.
- Transport
- Streamable HTTP, stdio
- Auth
- OAuth 2.1
- License
- Apache 2.0
The thesis
Tools should not care which model is calling them.
Model Context Protocol is the open standard that lets an AI system discover and use external tools at run time. Most teams treat it as a demo. efaimo treats it as infrastructure: one server, written once, that any model can call.
The same server runs in Claude, in your editor, and inside an agent you build. The integration lives in one place. Every model that speaks the protocol reaches it.
Architecture
A single hop between intent and action.
A host speaks to efaimo over one transport. efaimo handles discovery, auth, and routing, then speaks each tool's native protocol on the other side.
Registry
Open servers, ready to connect.
Every efaimo server is open source, versioned, and public. Point a client at one and it works. This is early and built in the open, so the list grows in public.
- efaimo/github live
Repos, issues, pull requests, and actions.
http - efaimo/postgres live
Read and write SQL with typed, scoped access.
stdio - efaimo/linear beta
Issues, projects, and cycles as tools.
http - efaimo/slack beta
Search, post, and react across channels.
http - efaimo/filesystem live
Sandboxed local files with allowlists.
stdio - efaimo/fetch live
Structured HTTP with schema checked output.
http - efaimo/cloudflare soon
DNS, Workers, and Pages from one server.
http - efaimo/notion soon
Pages and databases as first class tools.
http
Principles
Four commitments the protocol layer has to keep.
- 01
Open by default
Every server is Apache 2.0 and listed in a public registry. No lock in, no private fork of the protocol.
- 02
Interoperable, not captive
One server answers to any MCP client. Claude today, whatever speaks the protocol tomorrow.
- 03
Typed and observable
Tools ship JSON schemas, structured errors, and traceable calls. You can see what the model did.
- 04
Secure by construction
OAuth 2.1, least privilege scopes, and per tool allowlists are the default, not an upgrade.