---
title: "Overview"
description: "Work with Bauhow projects from ChatGPT, Claude, Perplexity, OpenCode, and Cursor."
---

The Bauhow MCP server connects AI applications to your Bauhow workspace. A client can read and create contacts, deals, and projects, and change planning-module inputs.

MCP stands for Model Context Protocol. The open standard defines how an AI accesses external applications. Bauhow provides a remote MCP server over Streamable HTTP and protects it with OAuth 2.1.

**[Capabilities](/en/mcp/capabilities)**

What the client can do, limits, and common workflows.

**[Example prompts](/en/mcp/prompts)**

Prompt patterns for common Bauhow tasks.

**[ChatGPT](/en/mcp/chatgpt)**

Add Bauhow as an app in Developer mode.

**[Claude](/en/mcp/claude)**

Connect Bauhow as a custom connector or in Claude Code.

**[Perplexity](/en/mcp/perplexity)**

Configure a custom remote connector.

**[OpenCode](/en/mcp/opencode)**

Add the server to your OpenCode configuration.

**[Cursor](/en/mcp/cursor)**

Use Bauhow through `mcp.json` in Cursor.

## Server URL

Every client uses the same URL:

```text
https://mcp.bauhow.com/mcp
```

You can also find the URL, with a copy button, in Bauhow under **Settings → Workspace → MCP server**. The server uses Streamable HTTP. There is no SSE endpoint and no local stdio server.

## Requirements

1. A workspace owner or admin turns on **Enable MCP server** under **Settings → Workspace → MCP server**.
2. You add the server URL to your AI client.
3. When connecting, you sign in to Bauhow and choose the workspace on the **Allow access** page.

You do not need an API key, client ID, or client secret. The AI client registers itself with Bauhow automatically the first time it connects.

:::warning
The MCP server works with the workspace's real data. Review write actions in the client before you approve them.
:::

## Sign-in and workspace selection

Bauhow uses OAuth 2.1 with PKCE. When you connect the client, a Bauhow window opens. If you are not signed in yet, sign in first. The **Allow access** page then shows:

- the name of the AI client
- the requested permissions
- a picker with your workspaces

Only workspaces with the MCP server enabled can be selected. The connection then applies to exactly that workspace. To use another workspace, connect the client again, for example by adding the server a second time.

## Permissions

| Permission | Meaning |
|---|---|
| `mcp:read` | Read contacts, buildings, deals, projects, and planning modules |
| `mcp:write` | Create and edit this data (includes read) |
| `offline_access` | Stay connected without signing in again |

Access tokens are valid for 15 minutes. The client refreshes them automatically.

Your role permissions in the workspace also apply. A request fails if your role lacks the required permission. For example, editing modules requires permission to edit projects.

## Cloud and local clients

ChatGPT, Claude (claude.ai and Claude Desktop), and Perplexity connect to Bauhow from their cloud infrastructure. Claude Code, OpenCode, and Cursor run locally on your computer. All clients use the same public URL `https://mcp.bauhow.com/mcp`.

## Revoke access

Under **Settings → Workspace → MCP server**, owners and admins see the **Connected clients** list. **Revoke access** blocks an individual client immediately. It must then be authorized again.

In addition:

- Disabling the MCP server for the workspace blocks all clients immediately.
- Removing a member from the workspace also blocks their clients.

Remove the connection in the AI client as well.
