MCP Comparison
Compare features, tools, and capabilities of these MCP servers side by side.
plugged.in MCP Hub — Proxy · Knowledge · Memory · Tools
The plugged.in MCP Proxy Server operates as a central hub that aggregates multiple Model Context Protocol (MCP) servers into a single, unified interface. It orchestrates knowledge, memory, and tools across connected MCPs, enabling clients to query documents, manage memory, and invoke tools from various servers through one connection. With support for STDIO, Server-Sent Events (SSE), and Streamable HTTP transports, it enables seamless integration with popular MCP clients like Claude Desktop, Cline, and Cursor while providing policy, telemetry, and registry features for scalable deployments. This proxy fetches tool, prompt, and resource configurations from the plugged.in App APIs and exposes a unified catalog of capabilities. It supports static built-in tools, memory clipboard operations, and dynamic tools discovered from connected MCP servers, including tool discovery, RAG-based search, document management, and notifications. The hub also offers configuration options for HTTP transport, authentication, and session management, making it possible to run as a stateless HTTP service or a stateful STDIO proxy, with optional API-key protection for HTTP endpoints.
Figma MCP server
The Figma MCP server enables design context delivery from Figma files to AI agents and code editors, empowering teams to generate code directly from design selections. It supports both a remote hosted server and a locally hosted desktop server, allowing seamless integration with popular editors through Code Connect and a suite of tools that extract design context, metadata, variables, and more. This guide covers enabling the MCP server, configuring clients (VS Code, Cursor, Claude Code, and others), and using a curated set of MCP tools to fetch structured design data for faster, more accurate code generation. It also explains best practices, prompts, and integration workflows that help teams align generated output with their design systems. The documentation includes concrete JSON examples for configuring servers in editors like VS Code and Cursor, as well as command examples for Claude Code integration and plugin installation.
| Feature | plugged.in MCP Hub — Proxy · Knowledge · Memory · Tools | Figma MCP server |
|---|---|---|
| Verified | ||
| Official | ||
| Tools Available | 17 | 8 |
| Has Installation Guide | ||
| Has Examples | ||
| Website | ||
| Source Code |
- pluggedin_discover_tools
- pluggedin_ask_knowledge_base
- pluggedin_send_notification
- pluggedin_create_document
- pluggedin_list_documents
- pluggedin_search_documents
- pluggedin_get_document
- pluggedin_update_document
- pluggedin_clipboard_set
- pluggedin_clipboard_get
- +7 more tools
- get_design_context
- get_variable_defs
- get_code_connect_map
- get_screenshot
- create_design_system_rules
- get_metadata
- get_figjam
- whoami
Can't decide? Check out both MCP servers for more details.