Skip to main content
Glama

pluggedin-mcp-proxy

smithery.yaml1.56 kB
# Smithery Cloud Deployment Configuration # Container-based deployment with custom Dockerfile # See: https://smithery.ai/docs/build/deployments/custom-container runtime: "container" # Build configuration build: dockerfile: "Dockerfile" dockerBuildPath: "." # Start command configuration # Note: Smithery expects the MCP server to be available at the root path (/) # Health checks are handled via Docker HEALTHCHECK directive in Dockerfile startCommand: type: "http" configSchema: type: object properties: PLUGGEDIN_API_KEY: type: string description: "Your Plugged.in API key for authenticated operations (get one at plugged.in/api-keys). Leave empty for tool discovery only." PLUGGEDIN_API_BASE_URL: type: string description: "Base URL for your Plugged.in instance (optional, defaults to https://plugged.in)" default: "https://plugged.in" REQUIRE_API_AUTH: type: string description: "Require API key authentication for HTTP requests (true/false)" enum: ["true", "false"] default: "false" # Metadata name: "Plugged.in MCP Hub" description: "A unified MCP hub that gives your AI Knowledge, Memory, and Tools — not just a proxy. Aggregate all MCP servers (STDIO, SSE, Streamable HTTP) into one connection while powering document-aware (RAG v2) and memory-augmented workflows across any client." homepage: "https://github.com/VeriTeknik/pluggedin-mcp" repository: "https://github.com/VeriTeknik/pluggedin-mcp" icon: "https://plugged.in/P-logo.png"

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/VeriTeknik/pluggedin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server