JetBrains vs Idaho Code
JetBrains is an MCP server published by GannaChernyshova. Marketplaces we read that list it: 1 (Docker MCP Catalog). Idaho Code is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   JetBrains |  Idaho Code |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:a662cac15c5d Forks (GitHub): 7 Pulls (Docker Hub): 59 235 Stars (Docker Hub): 2 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | JetBrains | Idaho Code |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 59 235 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 7 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | On your machine (mcp/jetbrains) | Remote server (gateway.pipeworx.io/idaho-code/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 30 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/gannachernyshova/mcp-jetbrains | github.com/pipeworx-io/mcp-idaho-code |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 15 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
JetBrains
A model context protocol server to work with JetBrains IDEs: IntelliJ, PyCharm, WebStorm, etc. Also, works with Android Studio.
Idaho Code
Idaho Statutes — state statutes by citation and by topic. Fleet #2747.
How to run each
JetBrains As a local MCP server: Docker image
claude mcp add --transport stdio jetbrains -- docker run -i --rm mcp/jetbrainsIdaho Code As a remote MCP server
claude mcp add --transport http idaho-code https://gateway.pipeworx.io/idaho-code/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Idaho Code has a remote endpoint we check. How we check endpoints
Tools each declares
Only JetBrains has
create_new_file_with_textexecute_action_by_idexecute_terminal_commandfind_commit_by_messagefind_files_by_name_substringget_all_open_file_pathsget_all_open_file_textsget_debugger_breakpointsget_file_text_by_pathget_open_in_editor_file_pathget_open_in_editor_file_textget_progress_indicators
Show the remaining 18
get_project_dependenciesget_project_modulesget_project_vcs_statusget_run_configurationsget_selected_in_editor_textget_terminal_textlist_available_actionslist_directory_tree_in_folderlist_files_in_folderopen_file_in_editorreplace_current_file_textreplace_file_text_by_pathreplace_selected_textreplace_specific_textrun_configurationsearch_in_files_contenttoggle_debugger_breakpointwait
Only Idaho Code has
ai_visibility_checkarchive_comparearchive_evidenceask_pipeworxask_pipeworx_betaask_pipeworx_groundedbet_researchclassify_rowcompany_factscompany_register_searchcompare_entitiesdeep_research
Show the remaining 31
discover_toolsentity_profileforgetgenerate_llms_txtid_searchid_statutekalshi_weather_edgelist_subscriptionspipeworx_feedbackpipeworx_trendingpolymarket_arbitragepolymarket_edge_trackerpolymarket_edgespolymarket_fill_riskpolymarket_kalshi_spreadrecallrecent_alertsrecent_changesrelease_calendar_marketsrememberresearch_rowresolution_auditresolution_diffresolve_entityscan_competitor_ai_presencescan_dependencysearch_withinsubscribesuggest_questionsunsubscribevalidate_claim
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Idaho Code as of 2026-10-16). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of Idaho Code publish no settings it asks for, so we do not compare settings.
What it can do: JetBrains · What it can do: Idaho Code · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.