[ Confirm upstream transport MCP ]

How to Use Plugged.in MCP Server with Bifrost

[ MCP SERVER SUMMARY ]

Plugged.in MCP server summary

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. Connect Plugged.in through Bifrost MCP Gateway to centralize access control, virtual keys, and tool-call observability for your AI assistants.

Property	Details
Company	Upstream maintainer
Connection type	Confirm upstream transport
Authentication	Varies by upstream server
Package or endpoint	See upstream documentation
Capabilities	Plugged.in tools over MCP, AI assistant connectivity, Governed tool access through Bifrost
Official documentation	Plugged.in MCP documentation

Before you start

Review the Plugged.in upstream documentation for its installation requirements
Obtain any credentials required by the upstream service
A running Bifrost MCP Gateway instance

What you can do with Plugged.in

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.
Expose Plugged.in tools to Claude, Cursor, and other MCP clients through one endpoint
Apply virtual keys, tool allowlists, and audit logging at the gateway

MCP ServerIntegration

[ HOW TO CONNECT ]

Connect Plugged.in to Bifrost in three steps

Install Bifrost

Start the gateway locally or deploy in your VPC.

npx -y @maximhq/bifrost

Add Plugged.in in MCP Gateway

Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and select the transport documented by the upstream server. Or register via the API below.

• Confirm the transport, command or endpoint, and authentication requirements in the Plugged.in upstream documentation.

• Replace every placeholder in the example before sending the request.

Point clients at Bifrost /mcp

Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Plugged.in.

{
  "mcpServers": {
    "bifrost": {
      "url": "http://localhost:8080/mcp",
      "headers": {
        "Authorization": "Bearer vk_your_virtual_key"
      }
    }
  }
}

[ EXAMPLE CONFIG ]

Register Plugged.in via API

Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.

# For a remote HTTP or SSE server:
curl -X POST http://localhost:8080/api/mcp/client \
  -H "Content-Type: application/json" \
  -d '{
    "name": "plugged-in",
    "connection_type": "<http|sse>",
    "connection_string": "<upstream MCP endpoint>",
    "tools_to_execute": ["*"]
  }'

# For a local STDIO server:
curl -X POST http://localhost:8080/api/mcp/client \
  -H "Content-Type: application/json" \
  -d '{
    "name": "plugged-in",
    "connection_type": "stdio",
    "stdio_config": {
      "command": "<upstream command>",
      "args": ["<arg>"]
    },
    "tools_to_execute": ["*"]
  }'

[ WHY BIFROST ]

Run Plugged.in through one governed gateway

Access control

Virtual keys, RBAC, and tool allowlists per team or agent.

Cost governance

Attribute MCP tool spend alongside LLM usage in one view.

Observability

Log every tool call with latency, server, and virtual key metadata.

Credential isolation

Upstream secrets stay in the gateway — not on every laptop.

[ FAQ ]

Common questions

What does the Plugged.in MCP server do?

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. The exact tools available depend on the upstream server version and configuration.

How do I connect Plugged.in to Bifrost?

Check the upstream documentation to determine whether Plugged.in uses STDIO, Streamable HTTP, or SSE. Then add it as an MCP client in Bifrost using the corresponding command or endpoint.