Japan Jepx MCP vs Context7
A side-by-side look at the Japan Jepx MCP and Context7 MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
J
Japan Jepx MCPDeveloper ToolsJapan JEPX electricity spot prices (system + 9 areas)45FairAuth: no auth requiredVerdict: choose Japan Jepx MCP for developer tools work; choose Context7 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?
JChoose Japan Jepx MCP when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
- You want tools like
get_latest_spot_price, get_spot_price_by_day, get_spot_price_history.
Choose Context7 when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
resolve-library-id, query-docs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | J Japan Jepx MCP | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 45/100 · Fair | 65/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 63,150 |
| Directory activity | 0 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 5 | 2 |
| Full listing | View Japan Jepx MCP | View Context7 |
Tools & capabilities
Japan Jepx MCP tools 5
get_latest_spot_priceLatest spot price for an area (default tokyo)get_spot_price_by_dayFull 48-period day curve + min/max/avgget_spot_price_historyDaily-average history (min/max/avg over window)get_cheapest_spotCheapest 30-min slots, or cheapest-area rankinglist_spot_areasArea catalogue + unit + latest date
Context7 tools 2
resolve-library-idResolves a general library name into a Context7-compatible library ID.query-docsRetrieves documentation for a library using a Context7-compatible library ID.
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.
Japan Jepx MCP
No confirmed install command for Japan Jepx MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Context7
{
"mcpServers": {
"upstash-context7": {
"command": "npx",
"args": [
"-y",
"ctx7"
]
}
}
}
Frequently asked questions
Japan Jepx MCP is categorized under Developer Tools and uses an install path we have not confirmed yet. Context7 belongs to Developer Tools and uses a local stdio subprocess. Pick Japan Jepx MCP for developer tools work and Context7 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. Japan Jepx MCP has no confirmed install command yet — follow its own setup instructions.
Japan Jepx MCP is listed as free. Auth: no auth required. Context7 is listed as free. Auth: api key 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 japan-jepx-mcp and upstash-context7 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Japan Jepx MCP has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Context7 has 65/100 (Great) with 9 views, 0 installs and 63,150 GitHub stars.