The 7Maps plugin for Claude Code, Cursor and Gemini CLI

Nothing to set up. After installing there is no account, no sign-in and no setting you need to fill in. The agent uses 7Maps when a task involves finding a tool, choosing, adding or connecting to an MCP server, or a configured server that fails, and leaves it alone otherwise. Servers that already work in your project are used directly, with no check.

Risk levels (read-only, needs approval, high risk) are automated estimates from each tool's public name, description and annotations. They can be wrong: treat them as a first check, not a security audit. How the map is made: methodology.

What the plugin contains: the address of the 7Maps MCP server (https://7it.co.il/7maps/mcp?set=agent, streamable HTTP: the eight tools an agent uses in a session, with short descriptions, so their definitions take about 2,000 tokens of the agent's context instead of about 11,600) and short instructions for the agent: the mcp-preflight skill and two optional commands in Claude Code, a rule in Cursor and a context file in Gemini CLI. No code runs on your machine, and there are no hooks or background processes.

/plugin marketplace add XLSV777/7maps
/plugin install 7maps@7maps

claude mcp add --transport http 7maps "https://7it.co.il/7maps/mcp?via=claude-code"

{ "mcpServers": { "7maps": { "url": "https://7it.co.il/7maps/mcp?via=cursor" } } }

gemini extensions install https://github.com/XLSV777/7maps

{ "mcpServers": { "7maps": { "type": "http", "url": "https://7it.co.il/7maps/mcp" } } }

The same Claude Code marketplace also lists 7IT Guard, the pre-launch check for a deployed web app: /plugin install 7it-guard@7maps. Each plugin installs and works on its own. Compare the plans.

Real, headless Claude Code runs on a fixed set of tasks, each run three ways: with the plugin, with the plugin and the /7maps:always section, and without the plugin. Tokens are what Claude Code itself reports for the whole task.

The plugin connects to the agent set (?set=agent): find_tool, route, road_conditions, watch, tool_card, preflight, report_road and my_7maps_usage. The other tools, including the ones for owners, are on the full server, https://7it.co.il/7maps/mcp. Servers can be named by URL, registry name or the vendor's plain name, such as "notion".

The first 20 calls a day of route and road_conditions are not charged, so the plugin works before an agent has a wallet. After that, the tools marked "Per call" are paid per call in USDC on Base through x402, by agents whose owner gave them a wallet (how). list_paid_tools returns the current prices. An agent without a wallet gets one line saying 7Maps cannot answer, and continues as usual.

Entirely optional. A personal key ties your agent's 7Maps calls to your own numbers: calls, servers checked, an estimate of the tokens saved and the failures avoided, by day, week and month, at 7it.co.il/7maps/me. It changes nothing about what a call costs, and 7Maps works the same without one.

1. Create a key at 7it.co.il/7maps/me. No account and no email; the key is shown once.
2. Claude Code plugin: paste it into the "7Maps key (optional)" setting when Claude Code asks for it. The setting is marked sensitive, so Claude Code keeps it in your system's credential store rather than in a settings file. It is sent as the X-7Maps-Key header.
3. Cursor, Gemini CLI, VS Code and other clients: add the header to the 7Maps server entry in your MCP settings (.cursor/mcp.json, ~/.gemini/settings.json, .vscode/mcp.json).

{ "mcpServers": { "7maps": { "url": "https://7it.co.il/7maps/mcp", "headers": { "X-7Maps-Key": "7m_your_key" } } } }

Then ask your agent to call my_7maps_usage, or open the dashboard. You can rotate the key or delete it, with every number tied to it, on the same page.

With 7IT Guard Pro, put your 7IT key in the same setting (in other clients, the X-7Maps-Key header): the paid 7Maps tools then run on your plan instead of per call, and the same key opens 7IT Guard.

The session hook (Claude Code, and Gemini CLI with the extension) downloads one public list, /7maps/down.json: short hashes of the servers 7Maps saw not answering. It hashes the servers configured on your machine and compares them there, so no server address, name or setting leaves your machine; it adds one line only when one of yours is on the list. Turn it off with SEVENMAPS_HOOK=off.

Security: every push to the public repository runs the package tests and a scan for secrets, with every build tool and test dependency pinned to an exact version. Text that 7Maps relays from other servers, such as tool descriptions, comes marked as untrusted text from that server, not instructions.

No mod: since October 2026 a Claude Code plugin can ship a mod, code that runs inside Claude Code with your permissions and outside its sandbox (Anthropic’s mods overview). The 7Maps plugin has none. Its Claude Code parts are a skill, two commands, the MCP connection and the session hook above, all readable in the public repository. When 7Maps covers skills and plugins, a plugin that ships a mod will be shown as code that runs on your machine, a supply-chain question, and not only as a token cost.

The opt-in sensors for MCP gateways are separate packages, not part of this plugin; their IP address is never stored either. Full details: the 7Maps sections of the privacy policy and the terms, and retention in the methodology.

Removing the plugin does not delete a personal key. To delete the key and its numbers, use "Delete my data" at 7it.co.il/7maps/me.

Bugs, questions and suggestions: open an issue on GitHub.

Privacy requests, data deletion and corrections to the map: lior@7it.co.il, as in the privacy policy. Server owners can also opt out of being checked at 7it.co.il/7maps/bot.

Every change: commits on GitHub.

7Maps by 7IT. Methodology. Claude, Claude Code, Cursor, Gemini CLI and VS Code are products of their respective owners and are named here only to say the plugin works with them. 7Maps is independent and is not made or endorsed by them.