mcpr MCP server
Commit Nov 7, 2026Synchronize Model Context Protocol server configurations across multiple AI editors and development tools from a single centralized configuration.
Also known as mathematic-inc/mcpr
- Stars
- 4
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 7, 2026
- License
- Apache-2.0
What is mcpr MCP?
mcpr is an MCP server. Synchronize Model Context Protocol server configurations across multiple AI editors and development tools from a single centralized configuration.
Summary generated from the project's README
About mcpr MCP server
Managing Model Context Protocol server configurations across multiple AI editors is what mcpr enables for developers. Instead of manually updating individual configuration files for every tool, you can define your servers in one central location and synchronize them to various clients. This CLI tool supports both stdio-based command-line servers and HTTP/SSE-based servers, allowing you to manage environment variables and custom headers through a single interface.
Developers can sync their setups to a wide range of applications including Claude Desktop, Cursor, VS Code, Windsurf, Zed, and Claude Code. The tool supports both global configurations and project-local setups using a local mcpr.json file. When you add or remove a server, the system performs atomic syncing to ensure your clients stay updated. This centralized approach eliminates the need to repeat configuration steps every time you switch between different AI-powered development environments.
What you can do with it
- 1Synchronize servers to multiple editorsPush your configured MCP servers to Claude Desktop and Cursor simultaneously.
- 2Configure project-specific toolsAdd an MCP server that only applies to your current working directory.
Written from the project's README. Every use case is checked against a quote from it.
Configuration
API_KEY
| Name | Description | |
|---|---|---|
| API_KEY | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablemathematic-inc/mcpr is public and reachablegithub.com/mathematic-inc/mcpr ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-07github.com/mathematic-inc/mcpr ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubMCPR - MCP Registry
A CLI tool for managing Model Context Protocol (MCP) servers across multiple AI-powered code editors and development tools.
Overview
MCPR provides a centralized way to configure and synchronize MCP server configurations to various client applications that support the MCP standard. Instead of manually editing configuration files for each tool, define your MCP servers once and sync them everywhere.
Features
- Centralized Configuration - Define MCP servers in one place, sync to all your tools
- Multi-Client Support - Works with Claude Desktop, Cursor, VS Code, Windsurf, Zed, and more
- Stdio & HTTP Servers - Support for both command-line and HTTP/SSE-based MCP servers
- Project-Local Configs - Global or per-project server configurations
- Shell Completion - Tab completion for commands and server names
- Atomic Syncing - Automatic sync to all clients after configuration changes
Installation
go install github.com/mathematic-inc/mcpr@latest
Or build from source:
git clone https://github.com/mathematic-inc/mcpr.git
cd mcpr
go build -o mcpr .
Quick Start
# Add a stdio-based MCP server
mcpr add stdio npx -y @modelcontextprotocol/server-filesystem /path/to/dir
# Add an HTTP-based MCP server
mcpr add http https://example.com/mcp --name my-server
# Sync to a client
mcpr client sync claude-desktop
# List configured servers
mcpr list
# List supported clients
mcpr list --clients
Commands
mcpr add
Add new MCP server configurations.
mcpr add stdio [command] [args...]
Add a stdio-based MCP server that communicates through standard input and output.
# Basic usage
mcpr add stdio npx -y @modelcontextprotocol/server-filesystem /home/user
# With custom name
mcpr add stdio --name filesystem npx -y @modelcontextprotocol/server-filesystem /home/user
# With environment variables
mcpr add stdio --env API_KEY=secret --env DEBUG=true npx my-server
# Add to local project config
mcpr add stdio --local npx my-project-server
Flags:
--name, -n- Custom name for the server (defaults to command name)--env, -e- Environment variables in KEY=VALUE format (repeatable)--local, -l- Add to local project configuration
mcpr add http [url]
Add an HTTP/SSE-based MCP server.
# Basic usage
mcpr add http https://example.com/mcp
# With custom name and headers
mcpr add http --name my-api --header "Authorization=Bearer token" https://api.example.com/mcp
Flags:
--name, -n- Custom name for the server (defaults to URL host)--header, -H- HTTP headers in Key=Value format (repeatable)--local, -l- Add to local project configuration
mcpr remove
Remove an MCP server from configuration. Alias: rm
mcpr remove my-server
mcpr rm my-server
After removal, all synced clients are automatically updated.
mcpr client
Manage client synchronization.
mcpr client sync [client-name]
Sync MCP servers to a client application.
# Sync all servers to a specific client
mcpr client sync claude-desktop
# Resync all previously synced clients
mcpr client sync
# Sync specific servers only
mcpr client sync cursor --servers server1,server2
# Sync to local client config
mcpr client sync claude-code --local
Flags:
--servers, -s- Comma-separated list of specific servers to sync--local, -l- Use local client configuration
mcpr client remove [client-name]
Remove a client from the sync list.
mcpr client remove cursor
mcpr client remove claude-code --local
Flags:
--local, -l- Remove from local configuration
mcpr list
Display configured items.
# List all configured servers
mcpr list
# List all supported clients
mcpr list --clients
mcpr list -c
Flags:
--clients, -c- List supported clients instead of servers
Supported Clients
| Client | Description | Local Config Support |
|---|---|---|
claude-desktop |
Claude Desktop app | No |
claude-code |
Claude Code CLI | Yes |
cursor |
Cursor editor | Yes |
windsurf |
Windsurf editor | Yes |
zed |
Zed editor | No |
vscode |
VS Code with GitHub Copilot | Yes |
continue |
Continue AI extension | No |
cline |
Cline VS Code extension | No |
codex |
OpenAI Codex CLI | No |
gemini |
Google Gemini CLI | No |
kilocode |
Kilo Code VS Code extension | No |
zencoder |
ZenCoder VS Code extension | No |
Configuration
File Locations
- Global config:
~/.config/mcpr/config.json - Local config:
mcpr.jsonin project directory (or parent directories)
Configuration Structure
{
"servers": [
{
"name": "filesystem",
"type": "stdio",
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/home/user"],
"env": {}
},
{
"name": "my-api",
"type": "http",
"url": "https://api.example.com/mcp",
"headers": {
"Authorization": "Bearer token"
}
}
],
"synced_clients": [
{
"name": "claude-desktop",
"local": false,
"servers": null
},
{
"name": "cursor",
"local": false,
"servers": ["filesystem"]
}
]
}
Server Types
Stdio Servers
Stdio servers communicate via standard input/output streams:
{
"name": "my-server",
"type": "stdio",
"command": "npx",
"args": ["-y", "my-mcp-server"],
"env": {
"API_KEY": "secret"
}
}
HTTP Servers
HTTP servers communicate via HTTP/SSE:
{
"name": "my-api",
"type": "http",
"url": "https://api.example.com/mcp",
"headers": {
"Authorization": "Bearer token"
}
}
Examples
Setting Up a Development Environment
# Add common MCP servers
mcpr add stdio --name filesystem npx -y @modelcontextprotocol/server-filesystem ~/projects
mcpr add stdio --name git npx -y @modelcontextprotocol/server-git
mcpr add stdio --name github npx -y @modelcontextprotocol/server-github --env GITHUB_TOKEN=ghp_xxx
# Sync to all your tools
mcpr client sync claude-desktop
mcpr client sync cursor
mcpr client sync vscode
Project-Specific Configuration
# In your project directory
cd ~/projects/my-app
# Add project-specific server
mcpr add stdio --local --name my-app-server ./scripts/mcp-server.js
# Sync to Claude Code's local config
mcpr client sync claude-code --local
Syncing Specific Servers
# Only sync certain servers to a client
mcpr client sync cursor --servers filesystem,git
How It Works
- Add servers to MCPR's central configuration
- Sync clients to copy server configs to each tool's native format
- Auto-resync happens when you add or remove servers
MCPR reads each client's existing configuration and updates only the MCP server sections, preserving all other settings.
Contributing
AI agents maintain this repository. Start with a GitHub Discussion and wait for a maintainer to review your proposal. If we accept it, a Mathematic maintainer or agent will open the pull request. GitHub restricts pull request creation to Mathematic maintainers and repository collaborators with write, maintain, or admin access, plus authorized maintenance agents.
When Mathematic implements a proposal, the implementation pull request will link to the Discussion and credit its original author.
See CONTRIBUTING.md for the full process.
License
Apache-2.0
This project is free and open-source work by a 501(c)(3) non-profit. If you find it useful, please consider donating.
mcpr MCP questions
Which AI editors are supported?
The tool supports Claude Desktop, Cursor, VS Code, Windsurf, Zed, Claude Code, and several others including Continue and Cline.
Can I use environment variables with my MCP servers?
Yes, you can add environment variables to stdio-based MCP servers using the --env flag.
Does it support both command-line and web-based servers?
Yes, it supports both stdio (command-line) and HTTP/SSE-based MCP servers.
How does it handle existing client configurations?
It reads the existing configuration of a client and updates only the MCP server sections, leaving other settings untouched.