One page per server: what it actually exposes to the agent, the config that scopes it down, and when connecting it is a bad idea.
An MCP server is a small process that exposes one system — a database, a repository, an issue tracker — to an AI coding agent through the Model Context Protocol. It decides what the agent can see and do in that system. The protocol is a tool interface, not a security boundary: whatever the server is allowed to do, the agent can do.
Every page in this section covers one server, and every one of them answers the same three questions: what it actually exposes, what the config should look like when you scope it down, and when connecting it is a bad idea.
We write these because vendor documentation almost always shows the permissive setup. It gets you to a working demo in five minutes and leaves you with an agent that can write to your production database. The interesting half — the part where you decide what to withhold — is usually left as an exercise.
Decide what the agent must not reach before you decide what it should. A read-only account with access to one schema is a different risk from a connection string with DDL rights, and the difference is invisible in the config file unless you go looking.
Telling an agent to only run safe queries is a suggestion. A database role that cannot write is a control. Anywhere the two disagree, the role wins — design for that.
The config you commit becomes the config everyone on the team runs. If it only works because of something on your machine, it will fail loudly for them, or worse, silently do something different.
supabase mcp server — what it means for a repo with real invariants, not a demo.
slack mcp server — what it means for a repo with real invariants, not a demo.
shopify mcp server — what it means for a repo with real invariants, not a demo.
puppeteer mcp server — what it means for a repo with real invariants, not a demo.
playwright mcp server — what it means for a repo with real invariants, not a demo.
notion mcp server — what it means for a repo with real invariants, not a demo.
mysql mcp server — what it means for a repo with real invariants, not a demo.
mongodb mcp server — what it means for a repo with real invariants, not a demo.
memory mcp server — what it means for a repo with real invariants, not a demo.
linear mcp server — what it means for a repo with real invariants, not a demo.
kubernetes mcp server — what it means for a repo with real invariants, not a demo.
hubspot mcp server — what it means for a repo with real invariants, not a demo.
google ads mcp server — what it means for a repo with real invariants, not a demo.
gitlab mcp server — what it means for a repo with real invariants, not a demo.
gcp mcp server — what it means for a repo with real invariants, not a demo.
filesystem mcp server — what it means for a repo with real invariants, not a demo.
fetch mcp server — what it means for a repo with real invariants, not a demo.
docker mcp server — what it means for a repo with real invariants, not a demo.
aws api mcp server — what it means for a repo with real invariants, not a demo.
atlassian rovo mcp server — what it means for a repo with real invariants, not a demo.