Skip to main content
Glama
ibeeger

persona-profile-mcp

by ibeeger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to persona-profile-mcp

No user-submitted related servers found.

    Related Servers

    • people-memory-mcp

      michelgrolet
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that gives AI agents a private, durable memory of people, providing a personal people graph in PostgreSQL with tools to search, remember, and connect people, plus imports from LinkedIn, Google Contacts, and WhatsApp, and a browser UI.
      11
      1
      MIT

    • rolodex

      mdostal
      A
      license
      Not graded
      quality
      A
      maintenance
      A local-first contact management MCP server with SQLite storage and Google Contacts sync, enabling AI agents to upsert, search, log interactions, and surface follow-ups for relationships.
      8
      MIT

    • Rapport MCP Server

      sssst1118
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to query local conversation transcripts and relationship data via a local MCP server, allowing retrieval of past conversations and facts about people.
      1
      AGPL 3.0

    • carddav-mcp

      dominik1001
      A
      license
      Not graded
      quality
      B
      maintenance
      A CardDAV MCP server that exposes contacts and address books as tools for AI assistants.
      136
      1
      MIT

    • tilde

      topskychen
      A
      license
      Not graded
      quality
      D
      maintenance
      A privacy-first MCP server that acts as the universal memory and profile layer for AI agents, enabling profile management, skills, resume import, and team sync.
      4
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    The tools are mostly distinct: search vs get vs list cover retrieval, create/update cover profile lifecycle, and add/update/delete cover facts. The main potential confusion is between add_facts (append new) and update_fact (modify existing), but the descriptions provide clear guidelines on when to use each. update_profile and update_fact are also distinct (profile-level vs fact-level).

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: search_profiles, get_profile, list_profiles, create_profile, update_profile, add_facts, update_fact, delete_fact. Retrieval verbs (search/get/list) and mutation verbs (create/update/add/delete) are cleanly separated with consistent snake_case.

    Tool Count5/5

    8 tools is a well-scoped set for a persona profile server. Each tool has a clear purpose covering retrieval, profile management, and fact management. The count is neither thin nor bloated for the domain.

    Completeness4/5

    The server covers the full lifecycle well: search/get/list, create/update for profiles, and add/update/delete for facts. The intentional absence of a delete_profile tool is documented as a design decision (with workaround guidance), and there's no glaring missing operation for the core workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources