Plugged.in

Install Plugged.in

Install instructions vary — visit the GitHub repository for the latest install command. Most MCP servers follow one of three patterns: npx -y <package> for Node, uvx <package> for Python, or docker run <image> for containerized servers.

Use Plugged.in with Claude Code

Once the server is on your machine, register it with Claude Code so the agent can call it like any other tool. The general pattern is:

claude mcp add plugged-in -- <install-command>

After it's registered, run claude and ask anything that requires Plugged.in. Claude Code will negotiate the MCP handshake and surface the server's tools, prompts, and resources to the model automatically. See our Claude Code MCP guide for environment variables, scope flags, and credential handling.

What this server is for

Plugged.in sits in the official servers category. It's officially maintained, which means breaking changes ship through proper releases and there's a real support channel. The full description from the source list:

A comprehensive proxy that combines multiple MCP servers into a single MCP. It provides discovery and management of tools, prompts, resources, and templates across servers, plus a playground for debugging when building MCP servers.

FAQ

Is Plugged.in free?

Yes — every MCP server in the ClawHire directory is open-source or freely available. Some servers proxy to paid APIs (you supply your own keys), but the server itself is free.

Does it work with Claude Desktop / Cursor / Windsurf?

If a client speaks the Model Context Protocol, it can use this server. The transport (stdio vs SSE vs HTTP) needs to match what the client supports, but the server itself is client-agnostic.

How do I report a bug or contribute?

Open an issue or PR on the GitHub repository.