Skip to main content
Glama

Related Servers

Alternatives to brief-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AI-native LinkedIn prospecting. It enables lead research, audience building, conversation management, and controlled outreach actions such as messaging and publishing through an OAuth-protected remote endpoint.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes MCP tools that give desktop agents durable two-tier memory with recall and graph traversal, project code intelligence (symbol lookup, impact walking, notes search), and web search with page-to-Markdown conversion. It also runs a local model gateway that routes Anthropic- and OpenAI-shaped traffic across providers with usage accounting.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to join and interact with online meetings (Zoom and Google Meet), capturing transcripts and recordings to generate meeting summaries.
      3
      10
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that exposes meetergo's scheduling and CRM API as tools for AI assistants, enabling Proton Calendar-backed booking management and contact operations without Google Workspace.
      37
      BSD 3-Clause
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP-native sales intelligence server enabling prospect enrichment, LinkedIn scraping, and CRM push to HubSpot/Salesforce via natural language.
      31 npm
      Mozilla Public 2.0

    TDQS

    A3.6/5.0

    Scored across 13 tools

    Disambiguation3/5

    Five tools all generate a 'brief' (get_meeting_brief, brief_with_history, brief_all_today, get_outlook_brief, enrich_brief_with_crm), and brief_with_history is explicitly a superset of get_meeting_brief. Descriptions do differentiate the data sources (Google vs Outlook vs CRM vs history), but an agent must read carefully to pick the right variant.

    Naming Consistency3/5

    Mostly snake_case verb_noun (get_upcoming_meetings, research_attendee, search_meeting_history), but the 'brief' family is inconsistent: brief_with_history, brief_all_today, get_meeting_brief, get_outlook_brief, enrich_brief_with_crm mix 'brief' as verb, noun, and modifier.

    Tool Count5/5

    13 tools is well-scoped for a meeting-intelligence server, and each tool covers a distinct capability (calendar fetch, research, search, brief, CRM, debrief).

    Completeness3/5

    Core read/brief/debrief flows are covered, but the action-item lifecycle is incomplete: get_open_action_items lists items yet no tool marks a follow-up done or closes an item, and there is no way to create or update meetings.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing