Skip to main content
The OpenRegister MCP Server enables AI assistants and agent frameworks to interact with the OpenRegister API through the Model Context Protocol. It exposes company search and data retrieval as tools that any MCP-compatible client can use. There are two ways to connect: the remote MCP server (no local setup needed) or the local npm package (for full control).

Remote MCP Server

The easiest way to connect — no local installation required. The server handles authentication via OAuth when you connect.

Use in AI Assistants

Connect directly in your browser — no terminal or config files needed.
Claude.ai supports MCP servers natively through its Integrations settings.
  1. Open Claude.ai and go to Settings → Integrations
  2. Click + Add or + Add Custom Integration
  3. Enter the URL: https://mcp.openregister.de/sse
  4. Follow the authorization flow to connect your API key

Use in Developer Tools

Edit a config file and restart your client. Requires Node.js 18+.
Edit your Claude Desktop configuration file:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
Restart Claude Desktop. Look for the hammer icon (🔨) to confirm the connection.

Build with It

Use the MCP server as a tool source in your own AI agents and pipelines.
The remote MCP server requires Node.js 18 or higher for mcp-remote. If you encounter connection issues, try clearing the MCP auth cache: rm -rf ~/.mcp-auth

Local MCP Server (npm)

Run the MCP server locally with your API key for full control. Repository: openregister-typescript/packages/mcp-server
For MCP clients that use configuration JSON (like Claude Desktop), add this configuration:

Authentication

Set your OpenRegister API key as an environment variable:
Get your API key from OpenRegister Keys. For more detailed configuration options and advanced usage, see the full repository documentation.