MCP.so
Sign In
P

PluggedinMCP

@VeriTeknik

About PluggedinMCP

No overview available yet

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "PluggedinMCP": {
      "command": "npx",
      "args": [
        "-y",
        "@pluggedin/pluggedin-mcp-proxy"
      ],
      "env": {
        "PLUGGEDIN_API_KEY": "<YOUR_PLUGGEDIN_API_KEY>"
      }
    }
  }
}

Tools

23

Get started with Plugged.in MCP - shows setup instructions and API key configuration (no API key required)

Triggers discovery of tools (and resources/templates) for configured MCP servers in the Pluggedin App.

Ask questions and get AI-generated answers from your knowledge base. Returns structured JSON with answer, document sources, and metadata.

Create and save AI-generated documents to the user's library in Plugged.in (requires API key)

List documents with filtering options from the user's library (requires API key)

Search for specific documents in your library. Returns document metadata (ID, title, snippet). To retrieve full content, use pluggedin_get_document with the returned document ID.

Retrieve a specific document's full content by ID. Use this after pluggedin_search_documents to get the complete content of documents you found. Set includeContent=true to get the full text.

Update or append to an existing AI-generated document (requires API key)

Send custom notifications through the Plugged.in system with optional email delivery. You can provide a custom title or let the system use a localized default.

List notifications from the Plugged.in system with optional filters for unread only and result limit

Mark a notification as done in the Plugged.in system

Delete a notification from the Plugged.in system

Set a clipboard entry by name (semantic key) or index (array-like). Named entries are upserted; indexed entries fail if index exists. Max 2MB per entry.

Get clipboard entries. Specify name or idx for a single entry, or omit both to list all entries with pagination.

Delete clipboard entries by name, index, or clear all entries.

List all clipboard entries with metadata. Image values are truncated to first 1000 chars for preview.

Push a value to the indexed clipboard with auto-incrementing index. Useful for building ordered pipelines or stack-like operations.

Pop the highest-indexed entry from the clipboard (LIFO behavior). Returns the entry value and removes it.

Start a new memory session to begin capturing observations. Returns a session UUID and memory_session_id for subsequent operations.

End a memory session and trigger Z-report generation (AI-compressed session summary).

Record an observation during a memory session. Observations are classified by the Analytics Agent into memory ring types (procedures, practice, longterm, shocks).

Search memories using semantic similarity. Returns lightweight results (50-150 tokens each) for token-efficient progressive disclosure. Use pluggedin_memory_details for full content.

Get full details for selected memories (progressive disclosure Layer 3). Use after pluggedin_memory_search to retrieve complete content for specific memories.

Overview

What is PluggedinMCP?

PluggedinMCP is a middleware proxy that aggregates multiple MCP servers into a single unified interface. It fetches tool, prompt, and resource configurations from the plugged.in App and routes requests to the appropriate underlying servers for any MCP client like Claude Desktop, Cline, or Cursor.

How to use PluggedinMCP?

Install and run with npx -y @pluggedin/mcp-proxy@latest --pluggedin-api-key YOUR_API_KEY. Then configure your MCP client (e.g., Claude Desktop, Cline, Cursor) to use the proxy as a server, setting the PLUGGEDIN_API_KEY environment variable or via command-line argument. Docker builds are also supported.

Key features of PluggedinMCP

  • Aggregates multiple MCP servers into one interface
  • Supports both STDIO and WebSocket MCP servers
  • Keeps servers organized with namespace prefixing
  • Allows switching between workspace configurations
  • Fetches capabilities from plugged.in App APIs
  • Handles tools, resources, resource templates, and prompts

Use cases of PluggedinMCP

  • Manage multiple MCP servers from a single MCP client
  • Switch between different sets of MCP configurations per workspace
  • Test connected servers using MCP Inspector via Docker
  • Centralize API key and configuration management with the plugged.in App

FAQ from PluggedinMCP

What runtime does PluggedinMCP require?

Node.js 18+ is required (v20+ recommended).

How do I get an API key for the proxy?

Obtain an API key from the plugged.in App at https://plugged.in/api-keys.

Can PluggedinMCP be run with Docker?

Yes. Build the image with docker build -t pluggedin-mcp-proxy:latest . and run it with the required environment variables (PLUGGEDIN_API_KEY, PLUGGEDIN_API_BASE_URL).

Does the proxy support STDIO and WebSocket servers?

Yes, it supports both STDIO (command-line) and WebSocket (HTTP-based) MCP servers.

How does PluggedinMCP handle multiple servers?

It uses namespace isolation with prefixed names (e.g., tool names) and resolves calls to the appropriate underlying server via the plugged.in App API.

Frequently asked questions

What runtime does PluggedinMCP require?

Node.js 18+ is required (v20+ recommended).

How do I get an API key for the proxy?

Obtain an API key from the plugged.in App at https://plugged.in/api-keys.

Can PluggedinMCP be run with Docker?

Yes. Build the image with `docker build -t pluggedin-mcp-proxy:latest .` and run it with the required environment variables (`PLUGGEDIN_API_KEY`, `PLUGGEDIN_API_BASE_URL`).

Does the proxy support STDIO and WebSocket servers?

Yes, it supports both STDIO (command-line) and WebSocket (HTTP-based) MCP servers.

How does PluggedinMCP handle multiple servers?

It uses namespace isolation with prefixed names (e.g., tool names) and resolves calls to the appropriate underlying server via the plugged.in App API.

Comments

More Other MCP servers