Xmp4 — Semantic Code Intelligence vs JCodemunch MCP
A side-by-side look at the Xmp4 — Semantic Code Intelligence and JCodemunch MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Xmp4 — Semantic Code Intelligence for developer tools work over a hosted endpoint; choose JCodemunch MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Xmp4 — Semantic Code Intelligence when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
xmp4_callees, xmp4_callers, xmp4_deps.
Choose JCodemunch MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
set_tool_tier, announce_model, jcodemunch_guide.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 2,804 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 16 | 6 |
| Full listing | View Xmp4 — Semantic Code Intelligence | View JCodemunch MCP |
Tools & capabilities
Xmp4 — Semantic Code Intelligence tools 16
xmp4_calleesFind direct callees (methods called by) a symbol in a project. Navigate step-by-step by calling xmp4_callees again on interesting results.xmp4_callersFind direct callers of a symbol in a project. Navigate step-by-step by calling xmp4_callers again on interesting results.xmp4_depsList external dependencies of a project.xmp4_grepServer-side regex text search over indexed project source files. Free tier: requires file_path (single file). Premium tier (XMP4_PREMIUM_GREP_WALK=true): allows file_glob multi-file walk. Prefer xmp4_tests_for/xmp4_usages for SCIP symbols — grep is for text not indexed (comments, literals, config keys).xmp4_guideUsage guide for xmp4 tools — read this first to learn the correct workflowxmp4_hierarchyGet type hierarchy (base, interfaces, derived) for a symbol in a project.xmp4_infoGet detailed information about a symbol in a project.xmp4_outlineGet outline (all symbols) for a file in a project.xmp4_projectsSearch and browse projects by language and name. Use this first to discover projects, then use other tools with the repo name.xmp4_searchSearch symbols in a project. Use xmp4_projects first to find the project identifier.xmp4_serverGet server information, version, and capabilitiesxmp4_sourceExtract source code for a symbol in a project.- +4 more on the listing page
JCodemunch MCP tools 6
set_tool_tierExplicit tier override for the current session. Narrows or widens the exposed tool list to 'core' / 'standard' / 'full'. Prefer plan_turn(model=...) for routine per-task use; use set_tool_tier only for an explicit override (e.g. escalate to 'full' after a capability-gated failure). A narrowing that costs more than it saves is refused.announce_modelAgent self-reports its active model identifier. Server resolves to a tier via model_tier_map (fuzzy: normalize → exact → glob → substring → '*' → 'full') and narrows the exposed tool list accordingly. Idempotent: a second call with the same model is a cheap no-op. Prefer calling plan_turn(model=...) for routine per-task use; use announce_model as a fallback when plan_turn is not appropriate for the current task.jcodemunch_guideReturn the version-current CLAUDE.md / AGENT.md policy snippet for jcodemunch-mcp — the same text produced by `jcodemunch-mcp claude-md --generate`. Lets an agent keep a one-line CLAUDE.md (e.g. "Call jcodemunch_guide and strictly follow its instructions.") instead of pasting a static snippet that drifts from the installed version. Idempotent, no repo context required. Matches the active tool surface, tier and disabled_tools — list 'jcodemunch_guide' in disabled_tools to hide it.orderDispatch any jcodemunch action by name: order(action, args). The single-verb front door to the full tool catalog. Read-only by default — actions that change index/session state require allow_state_change=true, and execution/file-write verbs are refused. For exploration questions ('how does X work'), order('get_ranked_context', {repo, query, token_budget}) answers in ONE call — prefer it over chained search/outline/source hops; add compress=true to fit more symbols in the same budget. Call 'menu' to discover actions, or 'route' to pick one from a task.menuDiscover catalog actions without keeping the full tool catalog resident: menu(query?). Returns compact rows (action, summary, required args, state_changing). With no query, lists the catalog. Pair with 'order' to dispatch the chosen action.routeMap a natural-language task to the best catalog action(s): route(task, repo?, execute?). Returns ranked recommendations with ready-to-run argument templates. With execute=true, dispatches the top recommendation and returns its result in the same call, collapsing discover-then-call into one round-trip. Recommends assemble_task_context / plan_turn for context-gathering intents.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Xmp4 — Semantic Code Intelligence
{
"mcpServers": {
"xmp4-semantic-code-intelligence": {
"url": "https://mcp.example4.ai/mcp"
}
}
}
JCodemunch MCP
{
"mcpServers": {
"jcodemunch-mcp": {
"command": "uvx",
"args": [
"jcodemunch-mcp"
]
}
}
}
Frequently asked questions
Xmp4 — Semantic Code Intelligence is categorized under Developer Tools and uses a remote HTTP/SSE transport. JCodemunch MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Xmp4 — Semantic Code Intelligence for developer tools work and JCodemunch MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Xmp4 — Semantic Code Intelligence has no declared pricing — check the project's own site. JCodemunch MCP has no declared pricing — check the project's own site. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add xmp4-semantic-code-intelligence and jcodemunch-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Xmp4 — Semantic Code Intelligence has a quality signal of 53/100 (Good) with 1 views, 0 installs and 1 GitHub stars. JCodemunch MCP has 67/100 (Great) with 0 views, 0 installs and 2,804 GitHub stars.