You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-9Lines changed: 5 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ Or choose [other installation methods](#-other-installation-methods) like `brew`
40
40
MCPM simplifies the installation, configuration, and management of Model Context Protocol servers and their configurations across different applications (clients). Key features include:
41
41
42
42
- ✨ Easy addition and removal of MCP server configurations for supported clients.
43
-
- 📋 Centralized management using profiles: group server configurations together and activate/deactivate them easily.
43
+
- 📋 Centralized management using profiles: group server configurations together and add/remove them to client easily.
44
44
- 🔍 Discovery of available MCP servers through a central registry.
45
45
- 🔌 MCPM Router for aggregating multiple MCP servers behind a single endpoint with shared sessions.
46
46
- 💻 A command-line interface (CLI) for all management tasks.
@@ -78,7 +78,6 @@ mcpm --version # Display the current version of MCPM
78
78
79
79
```bash
80
80
mcpm client ls # List all supported MCP clients, detect installed ones, and show active client
81
-
mcpm client set CLIENT # Set the active client for subsequent commands
82
81
mcpm client edit # Open the active client's MCP configuration file in an external editor
83
82
```
84
83
@@ -114,25 +113,22 @@ mcpm pop [SERVER_NAME] # Restore the last stashed server, or a specific one b
114
113
115
114
Profiles are named collections of server configurations. They allow you to easily switch between different sets of MCP servers. For example, you might have a `work` profile and a `personal` profile, each containing different servers. Or you might have a `production` profile and a `development` profile, each containing different configurations for the same servers.
116
115
117
-
The currently *active* profile's servers are typically used by features like the MCPM Router. Use `mcpm activate` to set the active profile.
116
+
The currently *active* profile's servers are typically used by features like the MCPM Router. Use `mcpm target set %profile_name` to set the active profile.
118
117
119
118
```bash
120
119
# 🔄 Profile Lifecycle
121
120
mcpm profile ls # List all available MCPM profiles
122
121
mcpm profile add PROFILE_NAME # Add a new, empty profile
123
122
mcpm profile rm PROFILE_NAME # Remove a profile (does not delete servers within it)
124
123
mcpm profile rename OLD_NAME NEW_NAME # Rename a profile
125
-
126
-
# ✅ Activating Profiles
127
-
mcpm activate PROFILE_NAME # Activate a profile, applying its servers to the active client
128
-
mcpm deactivate # Deactivate the current profile for the active client
124
+
mcpm add %profile_name # Add a profile to the active client
129
125
```
130
126
131
127
### 🔌 Router Management (`router`)
132
128
133
129
The MCPM Router runs as a background daemon process, acting as a stable endpoint (e.g., `http://localhost:6276`) that intelligently routes incoming MCP requests to the appropriate server based on the currently **active profile**.
134
130
135
-
This allows you to change the underlying servers (by switching profiles with `mcpm activate`) without reconfiguring your client applications. They can always point to the MCPM Router's address.
131
+
This allows you to change the underlying servers (by switching profiles with `mcpm target set %profile_name`) without reconfiguring your client applications. They can always point to the MCPM Router's address.
136
132
137
133
The Router also maintains persistent connections to MCP servers, enabling multiple clients to share these server sessions. This eliminates the need to start separate server instances for each client, significantly reducing resource usage and startup time. Learn more about these advanced capabilities in [Advanced Features](docs/advanced_features.md).
138
134
@@ -168,7 +164,7 @@ The MCP Registry is a central repository of available MCP servers that can be in
168
164
-[x] Basic server management (`mcpm add`, `mcpm ls`, `mcpm rm`)
169
165
-[x] Registry integration (`mcpm search`, adding by name)
0 commit comments