RoofKit MCP

Before you connect

RoofKit uses Model Context Protocol (MCP) to connect your AI client to your workspace. It is for signed-in workspace members. Your role, approved access, plan, and available credits still apply.

Included on paid plansRoofKit MCP is included on Pro, Ultra, and Enterprise plans. Free workspaces cannot connect. Each store reviews listings on its own schedule, so a store may not show RoofKit yet. The public marketplace and the direct connections below work in the meantime.

Use your RoofKit sign-inDo not paste rk_live_ Partner API keys into a plugin, client configuration, or agent chat. MCP uses OAuth, not Partner API keys. No client secret is required.

Review MCP Access

Sign in at https://app.roofkit.ai and select the workspace you want to connect. Open Settings, then MCP Access. New workspaces start with access on. An administrator who can manage integrations can turn access off.

Open MCP Access

Review workspace access and manage connected clients.

Install from your client

Install the RoofKit plugin from the plugin directory of your client. The plugin adds the RoofKit connection and workflow skills. Your first RoofKit request opens sign-in.

Claude, Claude Desktop, Cowork, and Claude Code: open the Claude directory and install RoofKit.
ChatGPT and Codex: open the plugin directory and install RoofKit.
Cursor: open the Cursor Marketplace and install RoofKit.

If your client does not list RoofKit yet, add the public marketplace verveai-hq/roofkit-plugins from GitHub in its plugin manager. In Claude Code, run the commands below.

Claude Code marketplace commands

claude plugin marketplace add verveai-hq/roofkit-plugins
claude plugin install roofkit@roofkit

Connect without a plugin

A direct connection adds the RoofKit tools without workflow skills. Use https://api.roofkit.ai/mcp. Claude, ChatGPT, Codex, and Claude Code identify themselves with a client metadata document, so a URL-only connection works. Cursor and the recipes below use a fixed public client ID. Choose one RoofKit connection per client to avoid duplicate tools. Use a current client release with HTTP MCP and static OAuth client ID support. If a command or setting below is unavailable, update the client first. These recipes do not certify a particular desktop version.

Claude and ChatGPT connectors

In Claude or ChatGPT, add a custom connector and enter https://api.roofkit.ai/mcp as the server URL. Leave the client ID and client secret empty. Then start sign-in from the connector.

Cursor desktop

Merge this entry into ~/.cursor/mcp.json for personal use, or .cursor/mcp.json for this project. Preserve your other servers. Open Cursor MCP settings, connect roofkit, and complete the browser authorization. The same client ID works in Cursor web and Cloud Agents.

Cursor MCP configuration

{
  "mcpServers": {
    "roofkit": {
      "url": "https://api.roofkit.ai/mcp",
      "auth": {
        "CLIENT_ID": "roofkit-cursor"
      }
    }
  }
}

Codex

Run these commands in the Codex CLI. They add a remote server and start OAuth sign-in. If adding the server already completes sign-in, skip the login command. Restart your Codex session after connecting.

Codex CLI commands

codex mcp add roofkit --url https://api.roofkit.ai/mcp --oauth-client-id roofkit-codex
codex mcp login roofkit

Claude Code

Run the command below for a personal connection. Open Claude Code, run /mcp, select roofkit, and authenticate in the browser. Do not add —client-secret.

Claude Code command

claude mcp add --transport http --scope user --client-id roofkit-claude roofkit https://api.roofkit.ai/mcp

What the plugin adds

The RoofKit plugin bundles the connection and workflow skills for setup, CRM, sites, reports, analytics, automations, and roof renders with estimates. A plugin does not grant workspace access. Each client still needs its own OAuth approval. If the plugin connection cannot complete OAuth, disable that connection and use a direct recipe. Keep only one active RoofKit connection.

Authorize and verify your workspace

Start authorization from the client. It opens a consent page on https://app.roofkit.ai. Sign in with your own RoofKit account. Do not open an empty consent URL manually or share the callback URL.
The consent screen shows the requesting client. For Claude, ChatGPT, and Codex it also shows the web domain that identifies the client. Approve only a connection that you started.
Verify the workspace shown on the consent screen and review the requested permissions. If the workspace is wrong, select the intended workspace in the RoofKit app and restart authorization from your client. Approve access, then return to the client.
Ask: “Show the company profile for my connected RoofKit workspace.” Confirm the company before requesting changes. This uses roofkit.workspace.profile.get and does not modify data.
Each authorization belongs to one user and one workspace. Changing the workspace in the RoofKit app does not move an existing connection. To switch, revoke the old grant and authorize again for the intended workspace.

What you can ask your agent to do

Area	Example request	What stays in RoofKit
CRM	List my latest leads, move a lead to the next stage with a follow-up date, and add a record to a Data Object.	Lead and Data Object tools create, update, link, and archive records with your permission. Quote and sales values need financial access. Each record keeps a change history that you can revert.
Sites	Show the copy of my main landing page and change its headline.	Saved site changes go live at once. Site delete, custom domain connection, and DNS changes open the app.
Reports	Find a measurement report and summarize its available details.	Agents can export a PDF, give a short-lived download link, import a report file, and share a customer link. Approval and geometry editing open the report editor.
Analytics	Build a dashboard of new leads by source, share its public link, and set a CPL target for a campaign.	Dashboard edits keep a version history that you can restore. Spend and CPL or CPA targets need financial access. Merging lead sources moves spend and can be reverted.
Automations	List my lead-table automations and help me find a run to retry.	Retries open the automation interface. Listing does not create or configure a routine.
Roof renders	Send a homeowner a photo upload link for a charcoal metal roof, then show me the render.	The homeowner uploads on a private RoofKit page. Each render consumes workspace credits.
Estimates	Estimate the roof replacement price for 123 Main St, Austin, TX 78701.	The estimate uses your workspace pricing and consumes workspace credits. It is not a final quote.
Workspace and team	Update the company address, change the email accent color, and invite a new sales rep.	An invitation sends an email at once. Role changes, member removal, billing, and ownership open the app.
Calls and connectors	Tag yesterday’s missed calls, set the source of a tracking number, and check why Google Ads spend stopped syncing.	Recording links last 15 minutes and every play is logged. Buying numbers and connecting accounts open the app.

Follow app handoffsWhen a tool returns an app link, open it and finish the step in RoofKit. A handoff does not mean the action is complete. Billing checkout, sensitive account changes, and credential setup require the app. Never paste provider credentials into the agent chat.

The MCP tool reference lists every tool with its access, kind, and arguments.

Roof renders and estimates without embeds

These tools work in AI clients that block embedded pages. The agent creates a private upload link, you send it to the homeowner, and the render comes back as an image in the chat. An estimate runs as a job from a US property address.

Render: roofkit.visualizer.upload_link.create, then roofkit.visualizer.upload_link.get until the render completes, then roofkit.visualizer.image.get.
Estimate: roofkit.estimates.create, then roofkit.jobs.get until the job succeeds. roofkit.estimates.get reads the saved estimate again later.

Private uploadsUpload links are tokenized, single use, and expire. Photos and renders stay in private RoofKit storage and never become public object URLs. A connection reads only the upload links and estimates that it created. Revoking the grant closes its open upload links.

Building your own homeowner app instead? Use the Partner API with a workspace API key. MCP is for workspace members.

Long jobs and retries

If a tool returns job_id, keep that ID and ask the agent to check roofkit.jobs.get until the job finishes or fails. Use the returned result or artifact link. A queued job is not a completed result. For a retry that accepts idempotency_key, reuse the original key. Do not repeat a create or credit-consuming operation to check its status. If the outcome is unclear, inspect the existing record or job first.

Revoke, update, or remove

In the connected workspace, open Settings → MCP Access. Find the client under Grants and select Revoke. Members can revoke their own grants. Administrators with integration management permission can revoke any workspace grant. Subsequent calls from that grant lose access. Revoking a grant does not uninstall a plugin. Uninstalling or disabling a client does not replace grant revocation. Revoke first when you want to stop access. To reconnect, start OAuth authorization again. Store and marketplace installs update through the plugin manager of your client. Remove the plugin through the same plugin manager. For a direct connection, remove only the roofkit entry from Cursor or use the commands below.

Remove a direct connection

codex mcp remove roofkit
claude mcp remove --scope user roofkit

Troubleshooting

Access unavailable: confirm that the workspace is on a Pro, Ultra, or Enterprise plan and that MCP Access is on. Changing a local client setting cannot enable service access.
OAuth or registration error: update your client and start authorization from the client again. For the direct recipes, check the fixed client ID. Do not substitute an API key.
Missing or forbidden tools: confirm the selected workspace, approved permissions, current role, and plan. Ask your administrator about access. A plugin cannot expand your permissions.
For other failures, email hello@roofkit.com with the client name, version, error code, and request_id if shown. Do not send tokens, API keys, callback URLs, or customer records.

Support and privacy

Email hello@roofkit.com for help with RoofKit MCP. The privacy policy at https://roofkit.ai/privacy describes how RoofKit handles workspace data, including data that a connected AI client reads.

Client documentation

Cursor desktop

Client configuration and installation reference.

Codex

Client configuration and installation reference.

Claude Code

Client configuration and installation reference.

Get started

Tools

Before you connect

Review MCP Access

Open MCP Access

Install from your client

Connect without a plugin

Claude and ChatGPT connectors

Cursor desktop

Codex

Claude Code

What the plugin adds

Authorize and verify your workspace

What you can ask your agent to do

Roof renders and estimates without embeds

Long jobs and retries

Revoke, update, or remove

Troubleshooting

Support and privacy

Client documentation

Cursor desktop

Codex

Claude Code

​Before you connect

​Review MCP Access

Open MCP Access

​Install from your client

​Connect without a plugin

​Claude and ChatGPT connectors

​Cursor desktop

​Codex

​Claude Code

​What the plugin adds

​Authorize and verify your workspace

​What you can ask your agent to do

​Roof renders and estimates without embeds

​Long jobs and retries

​Revoke, update, or remove

​Troubleshooting

​Support and privacy

​Client documentation

Cursor desktop

Codex

Claude Code

Before you connect

Review MCP Access

Install from your client

Connect without a plugin

Claude and ChatGPT connectors

Cursor desktop

Codex

Claude Code

What the plugin adds

Authorize and verify your workspace

What you can ask your agent to do

Roof renders and estimates without embeds

Long jobs and retries

Revoke, update, or remove

Troubleshooting

Support and privacy

Client documentation