A collection of Model Context Protocol (MCP) servers for enhancing AI tooling capabilities. These servers provide structured interfaces for AI
A collection of Model Context Protocol (MCP) servers for enhancing AI tooling capabilities. These servers provide structured interfaces for AI assistants to interact with various development tools and services. The mcp servers mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
The Model Context Protocol (MCP) is an open standard that enables AI assistants to securely connect to external data sources and tools. MCP servers expose specific functionality as tools that AI assistants can discover and use.
Everything the assistant can do here goes through one of these:
Socket — based detection of running instancesovermind_start — Start Overmind with optional configurationovermind_stop — Stop specific processes or all processesovermind_restart — Restart specified processesovermind_status — Get status of all processesovermind_quit — Gracefully quit Overmindovermind_kill — Forcefully kill all processesovermind_run — Run commands in Overmind environmentovermind_connect — Get connection instructions for processesovermind_is_running — Check if Overmind is runningovermind_check_procfile — Validate Procfile existence and contentsovermind_find_procfiles — Find all Procfiles in a directory treeSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Servers's toolset — Socket, overmind_start, overmind_stop and 11 more — is a fair guide to whether it matches your workflow. It is maintained by geoffjay; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Socket | based detection of running instances |
| overmind_start | Start Overmind with optional configuration |
| overmind_stop | Stop specific processes or all processes |
| overmind_restart | Restart specified processes |
| overmind_status | Get status of all processes |
| overmind_quit | Gracefully quit Overmind |
| overmind_kill | Forcefully kill all processes |
| overmind_run | Run commands in Overmind environment |
| overmind_connect | Get connection instructions for processes |
| overmind_is_running | Check if Overmind is running |
| overmind_check_procfile | Validate Procfile existence and contents |
| overmind_find_procfiles | Find all Procfiles in a directory tree |
| Server | Status |
| overmind | ✅ Stable |
{
"mcpServers": {
"overmind": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/geoffjay/mcp-servers#subdirectory=overmind",
"mcp-server-overmind"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.