Connect Claude

Configure Bauhow as a custom connector in Claude or as an MCP server in Claude Code.

Claude supports custom remote connectors in claude.ai, Claude Desktop, and the mobile apps. The connection originates from Anthropic’s cloud and uses the public Bauhow URL https://mcp.bauhow.com/mcp.

Free, Pro, and Max

Copy the MCP server URL

Make sure MCP is enabled in Bauhow under Settings → Workspace → MCP server and copy the displayed URL https://mcp.bauhow.com/mcp.

Open connectors

In Claude, open Settings → Connectors.

Add a connector

Select Add custom connector and paste the URL. You do not need a client ID or client secret. Claude registers itself with Bauhow automatically.

Connect

Save the connector and select Connect. Sign in to Bauhow, review the requested permissions on the Allow access page, choose the workspace, and approve.

Enable it in chat

Enable Bauhow for the current conversation from Connectors in the plus menu. Approve each tool request before allowing Claude to change project data.

Team and Enterprise

An owner or primary owner first adds the URL for the organization under Admin settings → Connectors → Add custom connector. Members then open Settings → Connectors, select Bauhow, and choose Connect to sign in with their own Bauhow account and choose their workspace.

Claude Code

Add the server in your terminal:

claude mcp add --transport http bauhow https://mcp.bauhow.com/mcp

Then start Claude Code, enter /mcp, and select bauhow to sign in. Claude Code opens your browser. Sign in to Bauhow, choose the workspace, and approve access.

First test

Use the Bauhow connector and call list_project_modules for project <PROJECT-ID>.
Show only each module's name and status. Do not change any data.

Troubleshooting

Connector not visible: On Team and Enterprise accounts, an owner must add the connector to the organization first.
Connection remains disconnected: Open Settings → Connectors and start the sign-in again with Connect.
Workspace cannot be selected: The Allow access page only lists workspaces with the MCP server enabled. Ask an owner or admin to enable MCP.
You need a different workspace: A connection applies to exactly one workspace. Add the connector again and choose the other workspace.

Source: Third party connectors with remote MCP