MCP Catalogs
Homepluggedin-app screenshot

pluggedin-app

by VeriTeknik·94·Score 48

A unified, self-hostable web interface for discovering, configuring, and managing MCP servers.

developer-toolsai-llmproductivity
15
Forks
3
Open issues
this month
Last commit
2d ago
Indexed

Overview

plugged.in is an AI Content Management System that transforms ephemeral AI interactions into persistent, versioned, and searchable organizational knowledge. It acts as a central hub connecting various AI clients with your knowledge base and the broader MCP ecosystem. The platform features an embedded RAG vector engine for document processing and semantic search, multi-model collaboration tracking, and universal MCP integration with over 1,500 servers.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:Centralizing AI conversations and knowledge from multiple AI models and platforms
you:Managing and versioning AI-generated content with proper attribution
you:Providing a unified interface for accessing and configuring MCP servers across different AI clients
you:What platforms does plugged.in support?
you:How does plugged.in handle data storage and security?

When to choose this

Choose plugged.in when you need a centralized hub to manage multiple MCP servers and transform AI conversations into persistent, searchable knowledge.

When NOT to choose this

Don't choose plugged.in if you need a lightweight solution with minimal dependencies or prefer a self-hosted solution without Docker requirements.

Tools this server exposes

12 tools extracted from the README
  • create_documentcreate_document(title: string, content: string, source?: string)

    Create a new document with version tracking and model attribution

  • query_ragquery_rag(query: string, limit?: number)

    Query the RAG knowledge base with semantic search

  • re_index_vectorsre_index_vectors(document_id?: string)

    Trigger re-indexing of document vectors for corrupted or missing embeddings

  • list_clipboard_entrieslist_clipboard_entries(visibility?: 'private' | 'workspace' | 'public')

    List all stored clipboard entries with optional filtering by visibility

  • get_clipboard_entryget_clipboard_entry(name: string)

    Retrieve a specific clipboard entry by name

  • set_clipboard_entryset_clipboard_entry(name: string, value: any, visibility?: 'private' | 'workspace' | 'public', ttl?: number)

    Store or update a clipboard entry with optional expiration and visibility settings

  • pop_clipboard_entrypop_clipboard_entry(name: string)

    Remove and return the last entry from a named clipboard stack

  • push_clipboard_entrypush_clipboard_entry(name: string, value: any)

    Add a new entry to a named clipboard stack

  • list_mcp_serverslist_mcp_servers(types?: string[], search?: string)

    Discover and list available MCP servers with advanced filtering options

  • test_mcp_servertest_mcp_server(server_id: string, tool_name: string, args?: any)

    Test a specific tool from an MCP server in the interactive playground

  • get_mcp_toolsget_mcp_tools(server_id: string)

    Retrieve all tools available from a specific MCP server

  • log_mcp_activitylog_mcp_activity(server_id: string, tool_name: string, request: any, response: any)

    Log detailed MCP interactions for debugging and analytics

Comparable tools

mcp-servernexusmcp-xmcp-hub

Installation

Docker Installation (Recommended)

git clone https://github.com/VeriTeknik/pluggedin-app.git
cd pluggedin-app
cp .env.example .env

docker compose up --build -d

Visit http://localhost:12005 after installation.

Claude Desktop Integration

Add the following to Claude Desktop's claude_desktop_config.json:

{
  "mcpServers": {
    "pluggedin": {
      "command": "docker",
      "args": ["run", "--rm", "-i", "veriteknik/pluggedin:latest", "mcp"]
    }
  }
}

FAQ

What platforms does plugged.in support?
plugged.in supports both amd64 and arm64 architectures via Docker, with automatic platform detection. It works with Claude Desktop, Cline, LM Studio, and other MCP-compatible clients.
How does plugged.in handle data storage and security?
The platform uses PostgreSQL 18 with pgvector for database storage and embedded zvec for vector search. All sensitive data is encrypted with AES-256-GCM, with per-profile encryption keys. It also supports OAuth 2.1 authentication.

Compare pluggedin-app with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.