Skip to content

Cursor registry-mcp — national company registries Prompt/explain_company

How to: Cursor registry-mcp — national company registries explain_company

client:Cursor transport:streamable-http prompt:explain_company

Add registry-mcp — national company registries to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "registry-mcp": {
      "url": "https://api.foretak.dev/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    explain_company is surfaced in the client's prompt or command menu. Unlike a tool, you invoke it deliberately — Cursor will not call it for you.

  3. 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.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Set these first

registry-mcp — national company registries will not start until these are set, so it never reaches Cursor.

  • 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.