MCP Config
Configure MCP servers for Claude Desktop, VSCode, and IntelliJ with one command.
Quick Start
# Install
pip install git+https://github.com/MarcusJellinghaus/mcp-config.git
# Setup for Claude Desktop
mcp-config setup mcp-code-checker "My Project" --project-dir .
# Setup for Claude Code (project-level)
mcp-config setup mcp-code-checker "My Project" --client claude-code --project-dir .
# Setup for VSCode (team projects)
mcp-config setup mcp-code-checker "My Project" --client vscode-workspace --project-dir .
# Setup for IntelliJ/PyCharm (GitHub Copilot)
mcp-config setup mcp-code-checker "My Project" --client intellij --project-dir .
# Setup filesystem server with reference projects
mcp-config setup mcp-server-filesystem "My Files" --project-dir . \
--reference-project docs=/path/to/docs \
--reference-project examples=/path/to/examples
Built-in Help System
Get comprehensive help directly from the CLI:
# Tool overview and commands
mcp-config help
# Help for specific commands
mcp-config help setup
mcp-config help remove
mcp-config help list
mcp-config help validate
# Help for server parameters
mcp-config help mcp-code-checker
mcp-config help mcp-server-filesystem
# Quick reference
mcp-config help mcp-code-checker --quick
Supported MCP Servers
- mcp-code-checker - Code analysis using pylint, pytest, and mypy
- mcp-server-filesystem - File system operations
- External servers via Python entry points
Documentation
- USER_GUIDE.md - Complete user documentation
- CONTRIBUTING.md - For developers enhancing mcp-config
Supported Clients
- Claude Desktop - claude_desktop_config.json (user-level)
- Claude Code - .mcp.json (project-level)
- VSCode - .vscode/mcp.json
- IntelliJ/PyCharm - GitHub Copilot mcp.json
Features
- 🔧 Multi-Client: Works with Claude Desktop, VSCode, and IntelliJ
- 🚀 Cross-Platform: Windows, macOS, and Linux support
- 📝 Simple: Standard JSON configuration
- Auto-detects Python environments and virtual environments
- Backs up configurations before changes
- Validates server setup with comprehensive checks
- Extensive CLI help system
License
MIT - see LICENSE file.
Metadata
Release files for mcp-config-tool 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mcp_config_tool-0.1.2.tar.gz | 170.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_config_tool-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 239.2 kB
Release files / mcp_config_tool-0.1.2.tar.gz
| Download URL | mcp_config_tool-0.1.2.tar.gz |
|---|---|
| Size | 170.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6709036850dda392f38504bc656c371a5cbab5e4cd808ed6fdfe1e6fe1b700ba
|
|
BLAKE2b-256 checksum How to use checksums |
e1930a24bd21369feabad171646e8a0e6b6b9cdda0cdb270e55919c9fc73126a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 22, 2026.
Transparency logRelease files / mcp_config_tool-0.1.2-py3-none-any.whl
| Download URL | mcp_config_tool-0.1.2-py3-none-any.whl |
|---|---|
| Size | 68.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d90ec47bce9ee9b4affb94d8c2910a3872fbaf9131ac85393f5dee9c4030a32e
|
|
BLAKE2b-256 checksum How to use checksums |
db3d95beeb20f0be19ecc7b4a3e70be8e28b0a8d9a01f58c4080fa533041d718
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 22, 2026.
Transparency log