Short answer
Teams should keep safe MCP config and setup notes in Git and keep secret values local. Cursor reads .cursor/mcp.json and Claude Code reads .mcp.json at the project root. AIPM does not install MCP config today; MCP packaging is planned.
Words used in this guide
- AIPM: a tool that installs and updates reusable AI instructions.
- Repository or repo: a project folder whose changes are saved and tracked.
- Git: a tool that records file changes so people can review or undo them.
- Config: settings that tell a tool how to work.
- MCP: a standard way for an AI tool to connect to other tools and information.
- Environment variable: a private setting stored on your computer, often used for a password or token.
What this means
MCP config connects agents to tools
MCP lets AI coding agents use external tools and data sources. That makes setup powerful, but it also means config needs review.
Do not commit secrets
A shared config can say which server to use and which environment variables are needed. It should not include real tokens, passwords, or private values.
Reuse the same setup across repos
Several projects may need the same MCP setup. Keep one reviewed copy of the safe settings and setup notes in Git and copy it into each repo; each project adds its own private values. AIPM installs skills today, not MCP config.
Simple steps
- Write what the MCP server does.
- List the safe config files.
- List required environment variables without values.
- Add a test step so users can confirm setup.
- Review the shared config in Git before other repos copy it.
Where to go next
If you want to try this in a real project, start with how to use AIPM and the command reference. If you want to share your own workflow, read the publishing guide.
FAQ
Can mcp.json be shared in Git?
Yes, if it does not include secrets. Keep private values in local environment variables or ignored files.
Can AIPM install MCP servers?
Not today. AIPM installs versioned skills into Claude Code and Codex (Cursor reads both folders) and tracks prompts. MCP server packaging is planned; until then, keep MCP config in Git.