Log inSubmit server
Pluggedin MCP Proxy logo

Pluggedin MCP Proxy

by VeriTeknik

Aggregates downstream MCP servers into one interface with unified discovery, document tools, notifications, and clipboard memory.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Pluggedin MCP Proxy

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "veriteknik-pluggedin-mcp-proxy": {
      "command": "npx",
      "args": [
        "-y",
        "@pluggedin/pluggedin-mcp-proxy@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

VeriTeknik/pluggedin-mcp-proxy MCP server aggregates multiple MCP servers behind one client connection and routes requests through the plugged.in App. It exposes built-in discovery, document, notification, and clipboard tools alongside tools, resources, templates, and prompts from connected servers. Downstream servers can use STDIO, SSE, or Streamable HTTP, while the proxy runs over STDIO by default or Streamable HTTP with optional authentication. Reach for it when you need centralized MCP configuration, cross-server discovery, document search, or a testing playground.

Use cases

  • Aggregate several MCP servers behind one client connection
  • Discover and refresh tools from connected servers
  • Search and manage documents through the plugged.in knowledge layer
  • Test MCP servers in the built-in playground
  • Switch between workspace-specific MCP configurations

Key features

  • Aggregates STDIO, SSE, and Streamable HTTP MCP servers
  • Exposes tools, resources, templates, and prompts
  • Provides document search and management tools
  • Supports notifications and clipboard-style memory tools
  • Runs over STDIO or Streamable HTTP
  • Offers cached capability discovery and refresh

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

19/20 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @pluggedin/pluggedin-mcp-proxy@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars138Stargazers on the source repository.
npm downloads541Package downloads in the last 30 days.
Last commit5mo agoMost recent push to the default branch.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Pluggedin MCP Proxy works

What VeriTeknik/pluggedin-mcp-proxy MCP server does

VeriTeknik/pluggedin-mcp-proxy MCP server combines several downstream MCP servers behind a single MCP endpoint. It obtains server capabilities and configuration through the plugged.in App, then directs calls to the server that provides each capability. This avoids configuring every downstream server as a separate connection in an MCP client.

The proxy covers the main MCP capability types: tools, resources, resource templates, and prompts. It also adds built-in functions for discovering connected tools, searching and managing documents, sending notifications, and maintaining clipboard-style entries that can act as a lightweight memory mechanism.

Document features connect to the plugged.in knowledge and RAG functionality. Supported operations include creating, listing, searching, retrieving, and updating documents. Document workflows can include model attribution, version relationships, visibility settings, metadata filtering, and semantic search with snippets, according to the repository description.

How it works

Connected servers may use STDIO, SSE, or Streamable HTTP. The proxy aggregates their available capabilities and presents a unified catalog to the MCP client. Discovery results are cached and can be refreshed when the connected server set changes.

VeriTeknik/pluggedin-mcp-proxy MCP server can run in STDIO mode or as a Streamable HTTP server. HTTP operation supports optional Bearer authentication and can use either stateful sessions or stateless operation. The project also describes OAuth token handling for Streamable HTTP servers, with tokens retrieved and managed through the plugged.in App.

The proxy includes a built-in playground for testing MCP servers with Claude, Gemini, OpenAI, and xAI. Inspector scripts and a health-check ping endpoint are also described as development and monitoring aids. Activity and tool calls can be reported through the plugged.in notification and analytics features.

Setup and configuration

The repository supports connecting the proxy to the plugged.in App, which supplies MCP server configuration and capability information. Downstream servers can be enabled or disabled through that ecosystem, and the proxy supports multiple workspaces for switching between configuration sets.

Clients can connect through the proxy's default STDIO transport or through its HTTP mode. HTTP deployments can configure a port, choose session behavior, and optionally require a Bearer token.

Tools and capabilities

Built-in capabilities listed by the project include:

  • Discovering available tools with cached results.
  • Searching the knowledge base and documents.
  • Creating, listing, retrieving, and updating documents.
  • Sending notifications, including optional email delivery.
  • Setting, getting, listing, pushing, popping, and deleting clipboard entries.
  • Aggregating dynamic tools from configured database, filesystem, API, and custom MCP servers.

The document system supports multiple file formats, source and AI-model filters, relevance scoring, content deduplication, visibility controls, and progress tracking. These features are provided through the plugged.in App rather than being limited to downstream server discovery.

Limitations and notes

VeriTeknik/pluggedin-mcp-proxy MCP server depends on the plugged.in App for configuration and several hub features. Its dynamic capabilities therefore depend on which downstream MCP servers are connected and enabled.

The project describes persistent memory as part of the hub direction, while the currently listed clipboard tools provide set, get, list, push, pop, and delete operations.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Pluggedin MCP Proxy

VeriTeknik/pluggedin-mcp-proxy is an MCP server that connects MCP clients to the plugged.in App and multiple downstream MCP servers through one interface. Its main tools discover connected capabilities, search and manage documents, send notifications, and operate a clipboard-style memory system. It also exposes tools, resources, templates, and prompts from configured servers.

It states that the proxy can run through STDIO, the default transport, or as a Streamable HTTP server, so use the repository's current setup instructions for installation and client configuration.

Yes, the README explicitly names Cursor as a supported MCP client. Cursor connects to the proxy and can access its built-in capabilities together with tools exposed by configured downstream MCP servers.

It supports STDIO, SSE, and Streamable HTTP across the proxy and downstream-server setup. The proxy itself runs over STDIO by default or Streamable HTTP, while connected MCP servers may use STDIO, SSE, or Streamable HTTP.

Yes, it provides document creation, listing, retrieval, updating, and search tools through the plugged.in knowledge layer. The documented RAG features also include filtering, snippets, model attribution, version relationships, and visibility controls.

Related MCP servers

All in Aggregators All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPluggedin MCP Proxy AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/veriteknik-pluggedin-mcp-proxy?style=directory)](https://allmcps.com/mcp/veriteknik-pluggedin-mcp-proxy)
HTML Embed
<a href="https://allmcps.com/mcp/veriteknik-pluggedin-mcp-proxy"><img src="https://allmcps.com/api/badge/veriteknik-pluggedin-mcp-proxy?style=directory" alt="Pluggedin MCP Proxy on AllMCPs" /></a>