Connect other MCP clients and scripts

Docs

Any client that speaks the Model Context Protocol can connect, with a sign-in for people and an API key for scripts and headless agents.

Construction AI's MCP server is a standard one: HTTP transport, OAuth 2.1 sign-in with PKCE and dynamic client registration for interactive clients, and a bearer token for anything that cannot open a browser.

The connector URL

https://app.constructionai.io/api/mcp

Interactive clients

Cursor, Zed, Claude Code with a browser and similar clients: add the URL as a remote MCP server and choose OAuth where the client asks. The client registers itself, opens the Construction AI sign-in, and you grant access on the consent screen. From then on it refreshes its own token.

Scripts and headless agents

A script cannot sit through a sign-in, so it authenticates with an API key instead:

In Construction AI open Settings, then Integrations, then API keys.
Create a key, give it the scopes it needs, and copy it once. It is not shown again.
Send it as a bearer token on every request:
```
Authorization: Bearer <your key>
```

The key carries your organisation and the scopes you gave it. Everything a key does is recorded in the audit log against the key, so give each integration its own.

What the server expects

MCP protocol version 2025-11-25 in the mcp-protocol-version header after initialize.
JSON-RPC over HTTP POST. No server-sent events are required.
Rate limits are per organisation and returned in the response headers.

The same data, two doors

Everything the MCP server offers is also on the public REST API, with the same authentication, the same scopes and the same audit log. Use MCP when an agent is doing the asking; use REST when a system is.

Microsoft 365 Copilot What your agent can see