Skip to main content
Glama
YangLiangwei

PersonalizationMCP

by YangLiangwei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to PersonalizationMCP

No user-submitted related servers found.

    Related Servers

    • blackmount-mcp by BlackMount-ai

      blackmount-mcpofficial

      BlackMount-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to access and search local browser history, bookmarks, open tabs, and downloads for personalized context.
      MIT

    • relic

      eXocriador
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI models and products to access Telegram and YouTube conversations, messages, searches, and transcripts through MCP and REST APIs, governed by per-product scopes, usage accounting, and response budgets.
      705 npm
      MIT

    • Personal DB MCP Server

      itoufo
      F
      license
      C
      quality
      D
      maintenance
      Provides structured personal data (skills, experiences, values) as context to AI services, enabling personalized outputs across different AI applications.
      100
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.7/5.0

    Scored across 88 tools

    Disambiguation4/5

    Most tools are clearly distinct due to platform prefixes (e.g., get_steam_library vs get_spotify_user_saved_tracks), but there are minor confusions between test_*_credentials, get_*_config, and generic status tools like test_connection and get_personalization_status. The unrelated 'add' tool also creates ambiguity.

    Naming Consistency3/5

    The majority follow a get_verb_noun pattern, but there are deviations like 'add', 'test_connection', and 'my_steam_recent_activity' (instead of get_my_...). The inconsistent use of 'my_' vs 'get_my_' and a few long auto-refresh names slightly reduce predictability.

    Tool Count1/5

    With 88 tools, this is an extreme mismatch even for a multi-platform personalization server. The calibration indicates 50+ tools as extreme, and this server has nearly double that, making it overwhelming for agents to navigate.

    Completeness4/5

    Each platform has a broad set of read operations and some actions (follow/unfollow, OAuth setup). Missing write operations like posting or creating playlists are notable, but for a personalization-focused server the coverage is substantial, with only minor gaps in content creation.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources