Loading ToolBench

Reading the current corpus…

granola-cli MCP server · F · ToolBench

← Browse

granola-cli

github.com/random1st/granola-cli

CLI client for Granola's official MCP server — meetings, transcripts, and notes from the terminal

2025-06-18+STREAMABLE_HTTP6 tools

40/100

Definition Quality35

Protocol Readiness65

Supportability31

Spec posture

Inferred effective spec 2025-06-18+·current baseline 2026-07-28

Static source inference · medium confidence · detected: Dynamic Client Registration

Deprecated protocol patterns detected

Summary

This is a CLI client, not an MCP server. The source shows a Rust CLI that CALLS an external Granola MCP server via rmcp client library (Streamable HTTP). Tool definitions are inferred from CLI command mappings in main.rs, not explicitly registered. Descriptions are minimal (5-20 chars), parameters lack type constraints and detailed descriptions, and no output schemas are documented. The code does not implement MCP server patterns, it consumes them.

Tools (6)

get_account_inforead onlyauthsource verified28/100

Get account info

get_meeting_transcriptread onlyauthsource verified38/100

Get transcript for a meeting

get_meetingsread onlyauthsource verified38/100

Get meetings by ID

list_meeting_foldersread onlyauthsource verified30/100

List meeting folders

list_meetingsread onlyauthsource verified38/100

List meetings

query_granola_meetingsread onlyauthsource verified37/100

Query meetings

Issues (5)

CRITICALtool ↗

This is a CLI client, not an MCP server. It consumes tools from an external Granola MCP server via rmcp HTTP client. Tool definitions are inferred from CLI command mappings, not explicitly registered with MCP server patterns.

list_meetingsget_meetingsget_meeting_transcriptquery_granola_meetingslist_meeting_foldersget_account_info

CRITICALtool-description ↗

All tool descriptions are under 20 characters ('List meetings', 'Get meetings by ID', etc.). Descriptions lack WHAT/WHEN/WHY context needed for LLM tool selection.

list_meetingsget_meetingsget_meeting_transcriptquery_granola_meetingslist_meeting_foldersget_account_info

HIGHconstrained-input ↗

Parameter descriptions are minimal ('Optional time range filter', 'List of meeting IDs to retrieve'). No format constraints, ranges, or examples. Parameters lack type specificity (e.g., 'time_range' is a string but no format documented).

Recommendations

Clarify: this repository is a CLI client for Granola's MCP server, not an MCP server itself. If the goal is to publish an MCP server, implement server-side tool registration with explicit schemas and descriptions.
Expand all tool descriptions to 50 - 200 characters. Example: 'list_meetings' → 'List all meetings in your Granola account, optionally filtered by time range or folder. Returns meeting IDs, titles, dates, and participant counts.'
Add parameter descriptions with format/constraint details. Example: time_range → 'ISO 8601 date range (e.g., 2024-01-01/2024-12-31) or relative (e.g., last_7_days, this_month).'
Document output schemas for each tool. Example: list_meetings returns {meetings: [{id, title, date, participants_count, folder_id}], total_count, next_cursor}.
Add error handling guidance in tool descriptions. Example: 'If a meeting_id is not found, the tool returns a 404 with available meeting IDs. Retry with a corrected ID or call list_meetings() to discover valid IDs.'

Score history

Overall score trend

First recorded score · v2 rubric

40/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	40	2025-06-18+	v2