Skip to main content
Glama
devli13

mcp-granola

by devli13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-granola

No user-submitted related servers found.

    Related Servers

    • Granola MCP Server

      EoinFalconer
      A
      license
      A
      quality
      D
      maintenance
      Integrates Granola.ai meeting intelligence with MCP clients to provide direct access to meeting notes, transcripts, and workspace organization. It allows users to search and retrieve meeting content through natural language by leveraging existing Granola credentials.
      7
      4
      MIT

    • openwhispr-mcp

      dezer32
      A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes OpenWhispr desktop app data—notes, folders, meeting transcripts, dictation history, and custom dictionary—to AI agents, with read and limited write operations.
      15
      205 npm
      MIT

    • Bruin

      sawzhang
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AI agents to read, write, and organize notes in a local-first, human-in-the-loop note-taking app.
      4 npm
      2
      MIT
    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

    A3.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_note retrieves a single note by ID, list_notes lists notes with filtering and pagination, and search_notes performs substring searches over note content. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_note, list_notes, search_notes) with clear, descriptive verbs. The naming is uniform and predictable, enhancing usability and reducing confusion.

    Tool Count3/5

    With only 3 tools, the server feels thin for a note management domain, as it lacks essential CRUD operations like create, update, or delete. While the tools are well-defined, the count is borderline low for comprehensive functionality.

    Completeness2/5

    The tool surface is significantly incomplete for note management, covering only read and search operations. There are no tools for creating, updating, or deleting notes, which are critical for a full lifecycle, leading to potential agent failures in workflows requiring modification.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources