Connect JetBrains IDE MCP Server endpoints and expose their tools to pi.
This server exposes 9 management tools for JetBrains IDE endpoints. While tool names follow verb_noun convention (status, reconnect, disconnect, set-url, add-endpoint, tools, use, unuse, selection), descriptions are extremely terse (5-15 chars) and lack actionable context. Input schemas are present but minimal, most parameters have only type and description, no enums or constraints. No output schemas documented. Error handling is absent from visible code. The server acts as a bridge/proxy rather than a domain tool, which limits its utility for agents. Most tools are configuration/lifecycle management rather than IDE interaction.
add a new endpoint, persist
close one or all endpoints
close one or all endpoints, reconnect, re-sync
show the project selection state
change URL of one endpoint, persist
per-endpoint state + tool count
list tools grouped by endpoint
deselect an endpoint (or every one) for this project
select an endpoint for this project (next session)
Descriptions critically short (5-15 chars). 'per-endpoint state + tool count' and 'list tools grouped by endpoint' lack WHEN to call, WHAT to expect, and prerequisites. LLMs cannot determine tool selection intent from these fragments.
No output schemas documented for any tool. Agents cannot plan downstream calls or extract required fields (e.g., endpoint IDs, tool names, connection state). Violates pattern:tool requirement.
No error handling guidance visible. Tools like reconnect and disconnect are destructive (WRITE risk) but lack recovery hints, retryability classification, or actionable error messages. Agents cannot self-correct on failure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | 2025-06-18+ | v2 |
Parameter descriptions missing or trivial. 'endpoint id' and 'new streamable-http URL' lack format constraints, valid ranges, or examples. No enum for 'id' in unuse (accepts 'all' or endpoint id, undocumented union type).
Tool names use generic verbs (status, tools, selection) that do not clearly distinguish from similar tools. 'status' vs 'selection' both report state; 'tools' vs 'selection' both list things. Naming lacks specificity per pattern:tool.