Edgible cards

Cards / needs / AI tools for assistants (MCP servers)

AI tools for assistants (MCP servers)

Self-hosted alternatives to Zapier MCP.

What people say

Why people self-host it

People leave hosted MCP platforms, Zapier MCP, keeping the server on one laptop for it. Why, strongest first: privacy, control, it has to run at home.

Does it suit a machine of your own?

Good fit an MCP server is a small web service next to the data it reaches, which is what Edgible publishes; what decides it is how the person's assistant signs in

Questions that decide it

How to publish it

Usually
api-key, which clients that can send a header use (Claude Code and most developer tools: Authorization: Bearer); Claude's desktop and web connectors expect the server's own OAuth instead, so check the client's current docs before choosing
When the data is private or sensitive
api-key, with read-only tools unless writes are needed, and one key per person so a key can be revoked; never none without the server's own sign-in

Who sees what inside it

every tool the server offers is something the assistant can do with the person's data; offer read-only tools first, and ask before tools that change or delete things

The machine

next to the data or tools it reaches; always on if others use it. Most packaged servers speak stdio, so publishing one needs a bridge container that serves it over Streamable HTTP; a server that already speaks HTTP needs none

For builders

the quickest way to let early users try an MCP server: publish it from the developer's machine or a small cloud server, without building hosting

Cards for it