# VeriTeknik/pluggedin-mcp-proxy [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://github.com/VeriTeknik/pluggedin-mcp-proxy  
**GitHub Stars:** 138  
**npm Downloads (last month):** 541  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/veriteknik-pluggedin-mcp-proxy

## Description
A comprehensive proxy server that combines multiple MCP servers into a single interface with extensive visibility features. It provides discovery and management of tools, prompts, resources, and templates across servers, plus a playground for debugging when building MCP servers.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "pluggedin-mcp-proxy": {
    "command": "npx",
    "args": ["-y","@pluggedin/pluggedin-mcp-proxy@latest"]
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/veriteknik-pluggedin-mcp-proxy/readme_