A comprehensive proxy that combines multiple MCP servers into a single MCP. It provides discovery and management of tools, prompts, resources, and
Plugged.In MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. A comprehensive proxy that combines multiple MCP servers into a single MCP. It provides discovery and management of tools, prompts, resources, and templates across.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Plugged.In is connected, these are the calls the assistant has available:
Prerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverCline — The Cline tool exposed by this serverCursor — For Cursor, you can use command-line arguments instead of environment variables:Authentication — When using --require-api-auth, include your API key as a Bearer token:Benefits — The Benefits tool exposed by this serverDocumentation — For complete deployment instructions, configuration options, troubleshooting, and technical details, see:You will need 5 environment variables: PLUGGEDIN_API_KEY, YOUR_API_KEY, PLUGGEDIN_API_BASE_URL, YOUR_SESSION_ID, YOUR_API_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Plugged.In's toolset — Prerequisites, Installation, Cline and 4 more — is a fair guide to whether it matches your workflow.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
| Cline | The Cline tool exposed by this server. |
| Cursor | For Cursor, you can use command-line arguments instead of environment variables: |
| Authentication | When using --require-api-auth, include your API key as a Bearer token: |
| Benefits | The Benefits tool exposed by this server. |
| Documentation | For complete deployment instructions, configuration options, troubleshooting, and technical details, see: |
{
"mcpServers": {
"pluggedin-mcp-proxy": {
"command": "npx",
"args": ["-y", "@pluggedin/pluggedin-mcp-proxy"],
"env": {
"PLUGGEDIN_API_KEY": "your-value",
"YOUR_API_KEY": "your-value",
"PLUGGEDIN_API_BASE_URL": "your-value",
"YOUR_SESSION_ID": "your-value",
"YOUR_API_BASE_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| PLUGGEDIN_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
| PLUGGEDIN_API_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| YOUR_SESSION_ID | Configuration value read at startup. | Optional |
| YOUR_API_BASE_URL | Endpoint or connection string the server talks to. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.