VS Code OneKeyAway: who controls this contract control_map
How to: VS Code OneKeyAway: who controls this contract control_map
Add OneKeyAway: who controls this contract to VS Code
-
01
Open .vscode/mcp.json and merge this in. Keep any servers already there.
{
"servers": {
"control": {
"type": "http",
"url": "https://onekeyaway.appin60.com/mcp"
}
}
}-
02
Save the file and restart VS Code.
-
03
Ask for something control_map does. VS Code lists the server's tools on connect and calls control_map itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that OneKeyAway: who controls this contract's identifier in your config matches the one above exactly.
Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 13 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.