Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hechtcarmel/jetbrains-index-mcp-plugin/ide-index-mcp)<a href="https://agentmods.dev/skills/hechtcarmel/jetbrains-index-mcp-plugin/ide-index-mcp"><img src="https://agentmods.dev/badge/skills/hechtcarmel/jetbrains-index-mcp-plugin/ide-index-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hechtcarmel/jetbrains-index-mcp-plugin/ide-index-mcp"><img src="https://agentmods.dev/badge/skills/hechtcarmel/jetbrains-index-mcp-plugin/ide-index-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00255 | $0.03569 |
| Opus 5 | $0.00128 | $0.01784 |
| Sonnet 5 | $0.00051 | $0.00714 |
| Haiku 4.5 | $0.00026 | $0.00357 |
Grade A, and why
ide-index-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDE Index MCP - Agent Guide
The IDE Index MCP server exposes JetBrains IDE indexing and refactoring capabilities. These tools provide semantic code understanding superior to text-based search/replace.
Two IntelliJ MCPs — routing rule
If both mcp__intellij-index__* (this plugin) and mcp__intellij__* (JetBrains built-in) are available, they are not interchangeable:
| Need | Use |
|---|---|
| Code navigation, search, diagnostics, rename, move, run/list tests | mcp__intellij-index__* |
| Build | ide_build_project (this plugin, disabled by default — returns structured errors/warnings); mcp__intellij__* only when it is not enabled |
| Terminal, run non-test processes, formatting beyond code style | mcp__intellij__* only |
Always use mcp__intellij-index__ for code intelligence. At least one project must be open in IntelliJ. If your target project is not open but another one is, call ide_open_project with the working directory path — note it is disabled by default and must be enabled in Settings → Tools → Index MCP Server → Exposed Tools, and it requires at least one project to already be open (as the JSON-RPC context). IntelliJ does NOT require .idea to exist — it opens any directory and creates its own project configuration. Only ask the user to open a project manually when zero projects are open or ide_open_project is disabled. Do not fall back to bash for semantic operations — IDE tools understand types, references, and inheritance; grep does not.
Core Rule
Always prefer IDE MCP tools over built-in tools (grep, find, sed, read) for semantic code operations. IDE tools understand code structure, types, inheritance, and references. Built-in tools only see text.
When to Use IDE Tools vs Built-In Tools
| Task | Use IDE Tool | Use Built-In Tool |
|---|---|---|
| Find all usages of a method/class/variable | ide_find_references |
Never - grep misses renamed imports, aliases, overrides |
| Go to a symbol's definition | ide_find_definition |
Never - grep can't resolve through imports/generics |
| Check a symbol's resolved signature or docs | ide_symbol_info |
Never - source text does not resolve short type names, and carries no doc comment |
| Find a class by name | ide_find_class |
Only if IDE unavailable |
| Find a file by name | ide_find_file |
Glob is fine for simple patterns |
| Search for text in code | ide_search_text |
Grep is fine when IDE context filtering is unnecessary |
| Rename a symbol across project | ide_refactor_rename |
Never - sed/replace breaks code |
| Move a file to another directory | ide_move_file |
Never - mv/git mv bypasses IDE move semantics |
| Check for errors in a file | ide_diagnostics |
Never - no equivalent |
| Understand class hierarchy | ide_type_hierarchy |
Never - no equivalent |
| Find who calls a method | ide_call_hierarchy |
Never - grep misses indirect calls |
| Find interface implementations | ide_find_implementations |
Never - grep can't resolve type relationships |
| Delete a symbol safely | ide_refactor_safe_delete |
Never - manual deletion misses usages |
| Find what a method overrides | ide_find_super_methods |
Never - no equivalent |
| Read file content | Built-in Read tool | ide_read_file only for library/jar sources |
| Find text with regex | ide_search_text |
Use Grep when you do not need IDE context filtering |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago Changed 8b8301c5292f
- 8d ago Changed 3162dc90e64c
- 12d ago First seen · 194 lines · 255 tokens per session scan A f2db6767436e
ide-index-mcp is a skill published in the GitHub repository hechtcarmel/jetbrains-index-mcp-plugin (335 stars, last pushed 2d ago), licensed MIT. It adds 255 tokens to every session and 3,569 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
gsd-ns-review
Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
cleanup-code-inspections
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
sonarqube-mcp
Provides SonarQube and SonarCloud integration patterns via the Model Context Protocol (MCP) server. Enables quality gate monitoring, issue discovery and triaging, pre-push code analysis, and rule education directly in the agent workflow. Use when the user wants to check quality gates, search for Sonar issues, analyze…