Buildr MCP server
Work with your Buildr projects, contacts, tasks, budgets, and forecasts from Claude, ChatGPT, Microsoft Copilot, or Grok. Sign in with your Buildr account. Included in every Buildr plan.
https://mcp.buildr.com/mcp You sign in with your normal Buildr login. No API keys to create or paste.
In Grok Bot, tell your bot: “Add a custom MCP server called Buildr at https://mcp.buildr.com/mcp.” Confirm, then click Authorize on the card it posts.
Using another AI? Add a remote MCP server with the URL
https://mcp.buildr.com/mcp and sign in with
Buildr when it asks. The
MCP guide has more detail.
Read and update records across Buildr, within your account's permissions.
You sign in with your Buildr account. Your AI sees and changes only what your account can.
They land on a change request your AI can't merge. A person reviews and merges it in Buildr. Other actions, like inviting bidders, happen right away.
The server can call Buildr's API and nothing else. It can't reach other systems or the open web.
The Model Context Protocol (MCP) is an open standard that lets AI like Claude, ChatGPT, Microsoft Copilot, and Grok connect to software the same way every time. Buildr hosts an MCP server, so you connect with one URL and your Buildr login.
No. Every Buildr plan includes it. You need your own account for the AI you connect.
Any app that supports remote MCP servers with OAuth sign-in, including Claude, ChatGPT, Microsoft Copilot Studio, Grok, and Grok Bot.
Kit is the AI agent built into Buildr, with review screens for leveling, scope, and budgets. The MCP server brings the same Buildr data into the AI you already use. Many teams use both.
New to MCP? Read what MCP means for a GC.
Add the URL to your AI and sign in with your Buildr account. Not on Buildr yet? Start a free trial.