> ## Documentation Index > Fetch the complete documentation index at: https://docs.baselayer.com/llms.txt > Use this file to discover all available pages before exploring further. # Claude > Connect Baselayer to Claude web, Desktop or Code, and run business verification from a chat. The same server works in Claude web, Claude Desktop, and Claude Code. In every case you sign in with your Baselayer account, so nothing here requires an API key. > [!NOTE] > > You need a Baselayer account with an active plan. If you do not have one, the sign-in page links to [self-serve sign-up](https://console.baselayer.com/signup). > > Custom connectors in Claude web and Desktop are available on all plans. On Team and Enterprise, only an organization Owner can add one, after which each member connects with their own Baselayer login. | Setting | Value | | - | - | | **Server URL** | `https://api.baselayer.com/mcp` | | **Authentication** | OAuth (sign in with your Baselayer account) | ## Claude Desktop & Web ### Entry point * Claude Desktop: click the **Connectors** icon in the left rail (the four-squares icon). The Connectors page opens on the **Discover** tab. * Claude web (claude.ai): * Free, Pro, and Max plans: open **Customize**, then **Connectors**, click **+**, and choose **Add custom connector**. * Team and Enterprise plans: an organization Owner opens **Organization settings**, then **Connectors**, clicks **Add**, and chooses **Custom**, then **Web**. Once added, each member opens the connector and clicks **Connect** to sign in with their own Baselayer login. ### Add Baselayer as a connector 1. Click **Add** in the top right. The **Add custom connector** dialog opens. 2. Enter **Baselayer** as the name and `https://api.baselayer.com/mcp` as the remote MCP server URL. 3. Under **Authentication**, select **Always required**. Every Baselayer tool needs a signed-in user. Do not pick "Required when the server asks" or "None". 4) Under **OAuth client**, select **Use your own OAuth client**. Enter the following values: | Field | Value | | - | - | | **OAuth Client ID** | `claude-connector` | | **OAuth Client Secret (optional)** | (leave empty) | The client ID is public and identical for every user. It carries no secret and grants nothing by itself; every tool call still runs as the person who signed in. > [!WARNING] > > Pick "Use your own OAuth client", not the recommended option. In Claude Desktop and Claude web, the default OAuth client option ("Use Anthropic's hosted client metadata") is not yet supported by Baselayer. Connect with Baselayer's pre-registered client ID, `claude-connector`, as described above. Claude Code is unaffected. 5. Leave **Managed authorization** off. (**Optional**) By default, tool calls run in your default organization's production application. To use a different organization, a sandbox application, or a federation instead, expand **Additional request headers** and click **Add header** for each one below, using the IDs from the Baselayer Console: | Header | Value | | - | - | | `X-Organization-ID` | the organization UUID | | `X-Application-ID` | the application UUID (e.g., sandbox application) | | `X-Federation-ID` | the federation UUID | Header values are stored by Claude and sent on every request alongside your OAuth token. They are not shown again after you save, so to change them remove the connector and add it again. A sandbox application returns the same deterministic test data the sandbox REST API does, and does not bill your account. See [Sandbox vs. production environments](https://docs.baselayer.com/docs/sandbox-vs-production-environments.md). Otherwise, leave **Additional request headers** empty and continue. 6. Click **Add**. Claude opens the Baselayer connector page, which reads "You are not connected to Baselayer yet". 7. Click **Connect**. Your browser opens the Baselayer sign-in page at id.baselayer.com. 8. Sign in with your Baselayer credentials. If you do not have an account, use the **Sign up** link on that page. 9. On the consent screen, review the access being granted ("Search and verify businesses with Baselayer on your behalf") and click **Allow**. 10. The browser returns you to Claude, and the connector page shows Baselayer as connected with its tools listed. In a chat, click the **+** button, choose **Connectors**, and make sure Baselayer is toggled on. Then try one of the **Example prompts** below. ### Remove Baselayer as a connector To sign out without deleting your configuration, open the Baselayer connector page from **Connectors** and click **Disconnect**. This revokes your session. To remove the connector entirely (required before you can change stored header values or switch OAuth client options), open the Baselayer connector page from **Connectors**, click the **⋮** menu, and choose **Remove**. ## Claude Code ### Add Baselayer as a connector 1. Add the server from a terminal. Use `--scope user` to make it available in every project, or omit it to register it for the current project only. ```bash theme={null} claude mcp add --transport http --scope user baselayer https://api.baselayer.com/mcp ``` (**Optional**) By default, tool calls run in your default organization's production application. To use a different organization, a sandbox application, or a federation instead, add the same headers as extra `--header` flags, using the IDs from the Baselayer Console: ```bash theme={null} claude mcp add --transport http --scope user baselayer https://api.baselayer.com/mcp \ --header "X-Organization-ID: " \ --header "X-Application-ID: " ``` 2. Start Claude Code, run `/mcp`, select **baselayer**, and choose **Authenticate**. A browser window opens for you to sign in and approve access. 3. Once it returns, `/mcp` shows the server as connected and lists its tools. 4. To confirm Baselayer is registered and connected, run: ```bash theme={null} claude mcp list ``` ### Working across profiles Servers registered with `--scope user` belong to the Claude Code configuration directory they were added under. If you use several profiles via `CLAUDE_CONFIG_DIR`, register Baselayer in each one you want it in. ### Remove Baselayer as a connector ```bash theme={null} claude mcp remove baselayer ``` ## Example prompts * "Verify Acme Holdings LLC at 500 Main St, Austin TX 78701 and tell me whether the EIN 12-3456789 matches." * "Run a full KYB on Acme Holdings LLC with website analysis and industry classification, then summarize the risk signals." * "Screen Jane Doe against OFAC and PEP." * "Check for UCC filings, tax liens, litigation, and bankruptcies against Acme Holdings LLC in Texas." * "Find Ray's Famous Pizza's website and social profiles and summarize what customers say in reviews." Claude picks the right tool from the [tool list](https://docs.baselayer.com/docs/mcp-tools.md) and polls for results when a product runs asynchronously, so you do not need to name tools yourself. ## Troubleshooting If the Baselayer sign-in page says "We are sorry... invalid request", the connector was added with "Use Anthropic's hosted client metadata" or with "No client ID, register one automatically". Remove it and add it again with **Use your own OAuth client** and the `claude-connector` client ID, as described above. If sign-in completes but the connector shows an error, your account must belong to an organization with at least one enabled application. Sign in to the [Console](https://console.baselayer.com) to confirm, then reconnect. If a tool returns "Caller lacks the required permission", your role does not include that product. The [permissions table](https://docs.baselayer.com/docs/mcp-tools.md#permissions) names the permission each tool needs; an organization admin can grant it in the Console under Members. If Claude Code's `/mcp` says the server is not found, check `claude mcp list` in the same profile you are running Claude Code from. A server added under one `CLAUDE_CONFIG_DIR` is not visible to another. If results come from the wrong organization, or from production instead of sandbox, check the request headers on the connector. Claude does not show saved header values, so remove the connector and add it again with the right IDs. For anything else, email [support@baselayer.com](mailto:support@baselayer.com). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.