MCP Comparison
Compare features, tools, and capabilities of these MCP servers side by side.
PersonalizationMCP
PersonalizationMCP is a unified personal data hub built on MCP (Model Context Protocol) that enables AI assistants to access and reason over data from Steam, YouTube, Bilibili, Spotify, Reddit, and more. This repository showcases a Python-based MCP server that aggregates platform APIs, manages OAuth2 tokens, and exposes a rich set of tools to query user data, playlists, watch history, and social actions. It emphasizes local data handling, token management automation, and a modular architecture that makes it easy to add new platforms through the @mcp.tool() decorator and server integration. Ideal for developers building context-aware assistants who want a single, extensible backend to surface personal data across multiple services. The MCP server is designed to run locally on your machine with secure configuration, offering multiple installation paths (conda, uv, or pip with virtualenv). It includes a comprehensive set of available tools organized by platform, robust token management (notably YouTube), and practical guidance for configuration, testing, and cursor-based integration with consumer apps like Cursor. The project also provides detailed setup steps for each platform, including how to obtain API keys, cookies, and OAuth credentials, ensuring a smooth path from zero to a functioning personal data hub.
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.
| Feature | PersonalizationMCP | plugged.in MCP Hub — Proxy · Knowledge · Memory · Tools |
|---|---|---|
| Verified | ||
| Official | ||
| Tools Available | 75 | 17 |
| Has Installation Guide | ||
| Has Examples | ||
| Website | ||
| Source Code |
- get_steam_library()
- get_steam_recent_activity()
- get_steam_friends()
- get_steam_profile()
- get_player_achievements(app_id)
- get_user_game_stats(app_id)
- get_friends_current_games()
- compare_games_with_friend(friend_steamid)
- get_friend_game_recommendations(friend_steamid)
- search_youtube_videos(query)
- +65 more tools
- 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
Can't decide? Check out both MCP servers for more details.