7Maps · Your key
See what 7Maps did for you.
A personal key ties your agent's 7Maps calls to your own numbers: calls, servers checked, tokens saved and failures avoided. No account, no email.
Create a key
7Maps works the same without a key. With one, the calls your agent makes carry it, and this page shows what they did. The key is random, shown once, and we keep only a one-way code of it.
Your key. Copy it now: it will not be shown again.
Use it with your agent
Claude Code plugin: /plugin marketplace add XLSV777/7maps, then /plugin install 7maps@7maps. Claude Code asks for the 7Maps key when the plugin is enabled (you can leave it empty); it is kept in your system's credential store.
Any MCP client: send the key as a header on the 7Maps connection.
{
"mcpServers": {
"7maps": {
"type": "http",
"url": "https://7it.co.il/7maps/mcp",
"headers": { "X-7Maps-Key": "7m_your_key" }
}
}
}
Claude Code, one line: claude mcp add --transport http 7maps https://7it.co.il/7maps/mcp --header "X-7Maps-Key: 7m_your_key". In a chat, the tool my_7maps_usage shows the same numbers. The key changes nothing about what a call costs.
Your numbers
Paste your key to see your dashboard. It is sent only to 7it.co.il, never in the address bar.
Dashboard
Tokens saved per day, last 30 days (estimate)
Share a badge
A small badge with the tokens 7Maps saved you this month, for a README or a profile. Off until you switch it on; it uses a separate public id, never your key.
Buy credit
Credit for paid calls, tied to this key. Not available yet.
Manage the key
Rotating gives you a new key with the same numbers. The current key stops working, so update it wherever you use it.
This deletes the key and every usage number tied to it. It cannot be undone.
Your new key. Copy it now: it will not be shown again.
How the numbers are counted
Tokens saved is an estimate. For each call we compare what the 7Maps answer cost in tokens with what your agent would realistically have spent to make the same decision without it: connecting to the one server in question and reading its tool list (measured by the map every day, with a ceiling), or a web search for a tool, never a whole directory. The share of your agent's context that 7Maps' own tool definitions take is subtracted, and each call has a ceiling. A server that was not answering and was skipped counts as a failed connection avoided. We count conservatively and never assume retries. Numbers from before 4 October 2026 used the first version of this estimate.
Failures avoided are servers not answering that a call steered your agent away from, risk changes caught by watch or verify_lock, and calls preflight showed would fail.
What is stored: a one-way code of your key, the date it was created, and for each call made with it the tool, whether it worked, the counts above and the response time. Never the task, the arguments, the results, your IP address or your user agent. Numbers are folded into daily totals; the raw per-call counts are deleted after about a month. "Delete my data" removes the key and every number tied to it at once. Details in the privacy policy and the terms.
7Maps by 7IT. Methodology.