# CrossBeam MCP server documentation and connection guide

> Connect eligible paid CrossBeam access to Claude, ChatGPT, or another Streamable HTTP MCP client and read completed plan-check results securely.

CrossBeam MCP is a read-only Model Context Protocol integration for eligible paying members. It lets an AI client retrieve completed plan-check results that the signed-in CrossBeam account is already allowed to view. It does not start reviews, modify findings, upload plans, or grant access to another user’s projects.

The Streamable HTTP endpoint is https://crossbeam-mcp.old-cherry-b095.workers.dev/mcp. The first connection opens a browser-based OAuth flow. Sign in with the same account used for CrossBeam; do not paste passwords, OAuth grants, or bearer tokens into a prompt.

## When to use the MCP server

- List completed CrossBeam projects visible to the signed-in account.
- Retrieve a project summary and its PASS, WARN, or FAIL findings.
- Inspect a finding’s evidence, citation, sheet reference, and annotations.
- Draft a corrections workflow using the completed review as source material.
- Search across results that the member or member organization can access.

## Available read-only tools

The server currently provides tool categories for project listing, project summaries, findings, finding detail, sheet annotations, corrections letters, search, and an in-client usage guide. Tool names and response shapes may evolve with the MCP server, so clients should discover tools through the protocol rather than hard-code an undocumented schema.

## Eligibility and access control

MCP is advertised as a paying-member feature. A member must have an eligible CrossBeam account and access to at least one completed review for the integration to return project data. Authentication does not broaden access: every project lookup is scoped to the signed-in user or that user’s CrossBeam organization.

CrossBeam results remain advisory. Agents should preserve citations and sheet references, distinguish CrossBeam findings from official agency decisions, and ask a qualified human to approve changes before relying on them for a permit submission.

## Connect a client

- Claude Desktop or claude.ai: add a custom connector with https://crossbeam-mcp.old-cherry-b095.workers.dev/mcp, then complete the browser sign-in.
- Claude Code: run “claude mcp add --transport http crossbeam https://crossbeam-mcp.old-cherry-b095.workers.dev/mcp”, then complete sign-in when prompted.
- ChatGPT: if the user’s workspace exposes custom MCP apps or connectors, use its current administrator-approved app setup to add the endpoint above and complete OAuth. Availability and controls vary by plan and workspace.
- Other clients: use Streamable HTTP and OAuth discovery. Do not configure the legacy SSE transport.

## Start with a scoped request

After connecting, ask the client to list visible CrossBeam projects or provide a known CrossBeam project identifier. A useful first request is: “Use CrossBeam to retrieve this project’s summary and FAIL findings. Keep every code citation and sheet reference, and separate the tool evidence from your own recommendations.”

- [CrossBeam developer resources](https://www.crossbeam-permits.com/developers): Current API, authentication, webhook, and machine-readable resource status.
- [CrossBeam help center](https://www.crossbeam-permits.com/help): Help with the web product and review workflow.
- [Contact support](https://www.crossbeam-permits.com/contact): Get help with membership eligibility or connection errors.
- [Log in to CrossBeam](https://www.crossbeam-permits.com/login): Access the CrossBeam account associated with the MCP connection.

---

Canonical URL: https://www.crossbeam-permits.com/developers/mcp
CrossBeam outputs are advisory. The authority having jurisdiction makes binding permit decisions.

Markdown URL: /developers/mcp.md