✦ Reach Out
Network Stack
Reach Out
Two paths in. Need an MCP server that isn't in the directory yet? Walk the brief below and we'll talk scope. Want to contribute, share feedback, get unstuck, or talk consulting? Skip to "Just Reach Out".
How It Works
From Request to Orbit
Every request follows the same path, from an idea to a working server in the directory.
01
Describe the server
Tell us what you want an assistant to be able to do, and which system
it should reach. "Read-only Arista EOS config and BGP state queries" is better
than "an Arista integration." Plain language, no hype.
02
We assess it
We look at fit (networking-adjacent), whether a usable API exists to build
against, and the safety surface. Not every request can be built, but every
one gets read.
03
We reach out & build it
We email you at the address you give us to talk through your request, scope,
safety, and whether it ships as read-only or read/write.
Request a Server
The Brief
Tell us what you need. The more specific the better, name the platform, the API, the tools you'd want.
Just Reach Out
Other Reasons to Get in Touch
The brief above is for server requests. Everything else lives here. Pick the closest fit, then send a note below or connect on LinkedIn.
✦ Contributors
Help maintain or expand the collection
Want to help maintain an existing server, add a vendor that
isn't in the directory yet, or improve the site itself? Tell
me what you have in mind and we'll scope it together.
✦ Feedback
Tell me what's off, or good
Something missing, wrong, or maybe you found the content really helpful. Please let us know.
✦ Help & Consulting
Setup help or consulting
Stuck on an install step, the Docker MCP Gateway, or a tool that
isn't behaving the way the page says it should? Drop the details
and I'll see if I can unblock you. For production rollouts,
hardening, or scoping a deployment, happy to talk consulting too.