pluggedin-mcp-proxy

Pluggedin Proxy MCP Server

pluggedin-mcp-proxy unifies access to configured MCP servers for developers using Claude Desktop, Cline, or Cursor. Its tools cover discovery, document retrieval and editing, notifications, and persistent memory for AI workflows.

Server facts

pluggedin-mcp-proxy

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
136
Last commit
Data as of

Overview

Server configurations in the plugged.in App drive pluggedin-mcp-proxy's routing, connecting client requests to the appropriate downstream MCP service. Discovery brings built-in tools and connected server capabilities together, while the hub also handles resources, resource templates, and prompts. Document workflows can begin with a library search that returns identifiers, titles, and snippets, followed by retrieval of the full content. The knowledge-base tool produces answers accompanied by document sources and metadata. Other library tools support filtered listings, document creation, and changes or additions to existing AI-generated documents.

Memory tools support a capture-and-recall workflow: start a session, record observations, and end it to trigger an AI-compressed session report. Semantic search returns brief memory results, with a details tool available for retrieving selected entries in full. Clipboard tools store values under names or indexes and provide push/pop operations for ordered pipelines and stack-style handling. Notifications can be sent through Plugged.in with optional email delivery, then listed, marked done, or deleted.

pluggedin-mcp-proxy setup notes

  • pluggedin-mcp-proxy records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers