Gemini CLI registry-mcp — national company registries Prompt/register_coverage
How to: Gemini CLI registry-mcp — national company registries register_coverage
Add registry-mcp — national company registries to Gemini CLI
-
01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"registry-mcp": {
"httpUrl": "https://api.foretak.dev/mcp"
}
}
}-
02
Save the file and restart Gemini CLI.
-
03
register_coverage is surfaced in the client's prompt or command menu. Unlike a tool, you invoke it deliberately — Gemini CLI will not call it for you.
-
04
If it does not appear, check that registry-mcp — national company registries is connected and that you are looking at its prompts rather than its tools.
Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs
Set these first
registry-mcp — national company registries will not start until these are set, so it never reaches Gemini CLI.
-
REGISTRY_MCP_CONTACT_EMAIL -
REGISTRY_MCP_CACHE_PATH -
COMPANIES_HOUSE_API_KEY -
BOLAGSVERKET_CLIENT_ID -
BOLAGSVERKET_CLIENT_SECRET -
BOLAGSVERKET_ENVIRONMENT
Same prompt, other clients
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.