companies-house

This MCP server provides programmatic access to UK Companies House data via the Companies House API, exposing 45+ endpoints for company information, searches, officers, filings, PSCs, charges, and more. You can query company profiles, registered addresses, filing histories, PSC details, officer appointments, and financial data such as charges and registers through the MCP endpoints. The server is designed to be consumed by MCP clients, returning structured responses that map to the underlying Companies House resources. Use the available tools to perform targeted lookups (by company number, name, or officer), run advanced searches with filters, and retrieve historical records across the various resource types. To use it in Claude Desktop or other MCP clients, configure the MCP server under mcpServers with the appropriate command, arguments, and your API key.

Available tools cover:

• Company Information: get_company_profile, get_registered_office_address, get_registers, get_insolvency, get_exemptions, get_uk_establishments
• Search Capabilities: advanced_company_search, search_all, search_officers, search_disqualified_officers, alphabetical_search, dissolved_search
• Officers & Appointments: get_officers, get_officer_appointment, get_officer_appointments_list, get_corporate_officer_disqualification, get_natural_officer_disqualification
• Filing & Documents: get_filing_history, get_filing_history_item
• Ownership & Control: get_persons_with_significant_control, get_psc_individual, get_psc_corporate_entity
• Financial: get_charges, get_charge_details Each tool accepts a JSON payload describing the query parameters (e.g., company_number, query, date ranges) and returns the corresponding data from Companies House.

Prerequisites:

• Node.js and npm installed on your system
• Access to the internet to install the MCP server package
• A Companies House API key (registered at the Companies House Developer Hub)

Install using npm (global install):

npm install -g companies-house-mcp-server

Run directly with npx (recommended):

npx companies-house-mcp-server

If you prefer to build from source (optional):

git clone https://github.com/stefanoamorelli/companies-house-mcp.git
cd companies-house-mcp
npm install
npm run build

Then configure Claude Desktop or your MCP client to point to the built index (example path) and supply your API key via environment variable as shown in the configuration example.

Configuration example for Claude Desktop (using npx):

{
  "mcpServers": {
    "companies-house": {
      "command": "npx",
      "args": ["-y", "companies-house-mcp-server"],
      "env": {
        "COMPANIES_HOUSE_API_KEY": "your_api_key_here"
      }
    }
  }
}

Building from source and using the built server in Claude Desktop:

{
  "mcpServers": {
    "companies-house": {
      "command": "node",
      "args": ["/absolute/path/to/companies-house-mcp/dist/index.js"],
      "env": {
        "COMPANIES_HOUSE_API_KEY": "your_api_key_here"
      }
    }
  }
}

Tips and caveats:

• Always keep your Companies House API key secure; do not commit it to version control.
• The server exposes many resources; start with a few essential endpoints (e.g., get_company_profile, search_all) to validate connectivity.
• If you encounter rate limits from the underlying API, consider caching responses in your MCP client or staggering requests.
• Ensure the API key has the necessary permissions for the endpoints you intend to use (some endpoints may require elevated access).
• For local development, you can run the server with npx and override the API key via environment variables in your MCP client configuration.
• When upgrading the MCP server package, review the change log for any breaking changes in parameter names or response formats.
• If using Claude Desktop, the mcpServers config should mirror the examples, and you can switch between npx and node-based execution depending on whether you’re using a prebuilt binary or a development build.