MCP Server Unified Deployment Open Source Project
Connect Unified Deployment to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP Server Unified Deployment Open Source Project. The unified deployment mcp server is what makes that connection.
A unified deployment and management tool for MCP (Model Context Protocol) servers. This project converts MCP servers deployed in various forms (uvx, npx, etc.) into a standardized SSE (Server-Sent Events) deployment, facilitating unified invocation by different tools.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Features — The Features tool exposed by this serverExample — The Example tool exposed by this serverUsage — This script will create configuration files for each client found in the mcp_servers.json file and place them in the config/client_configs/Configuration — The Configuration tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at based on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: DEBUG. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
mcp-proxy, it is recommended that mcp-proxy be installed through pipx). - uvx (for uvx based servers) - Docker and Docker Compose (optional, for containerized deployment)This sits in the file and storage access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Unified Deployment's toolset — Features, Example, Usage and 1 more — is a fair guide to whether it matches your workflow. It is maintained by BigUncle; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Unified Deployment's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Features | The Features tool exposed by this server. |
| Example | The Example tool exposed by this server. |
| Usage | This script will create configuration files for each client found in the mcp_servers.json file and place them in the config/client_configs/ directory. The generated configuration files are named mcp_<client>_*.json, wher |
| Configuration | The Configuration tool exposed by this server. |
{
"mcpServers": {
"server-unified-deployment": {
"command": "uvx",
"args": ["based"],
"env": {
"DEBUG": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
mcp-proxy, it is recommended that mcp-proxy be installed through pipx). - uvx (for uvx based servers) - Docker and Docker Compose (optional, for containerized deployment)| Variable | Description | Required |
|---|---|---|
| DEBUG | Configuration value read at startup. | Optional |
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.