Skip to main content

MCP Server

Connect VH3 AI to Claude and ask about your jobs, engineers, sites, customers, quotes and invoices in plain English. Claude calls VH3 AI tools through the Model Context Protocol (MCP), and every answer comes from your own company’s data. Most people connect in Claude with a VH3 sign-in and nothing to install. Developers who use Cursor, Claude Code, n8n or a custom agent can connect with a token under Advanced: developer access.

Connect in Claude

Choose the route that suits you. All three use the same VH3 account and give you the same tools.
Works on claude.ai, Claude Desktop, Claude mobile and Cowork. Your plan needs to allow custom connectors; on Team and Enterprise plans an owner adds the connector once for the organisation.
1

Open the connector settings

In Claude, open Customize → Connectors and choose Add custom connector.
2

Enter the VH3 AI details

Name it VH3 AI and use this server URL:
3

Connect and sign in

Choose Add, then Connect, and sign in with your VH3 account.

Sign in with your VH3 account

A VH3 AI page opens in your browser. Enter the email and password you use for VH3 Connect. Your password goes to VH3 only. If sign-in fails, check the message on the page:

Choose what Claude may do

After sign-in, the page asks what to allow.
  • Read access is always granted. Claude can read jobs, engineers, sites, customers, quotes, invoices and reports for your company, and runs these tools without asking each time.
  • Allow actions appears only when VH3 AI offers a tool that can act for you, such as Ask Connie, which can send email and SMS, create drafts and queue quotes. It is unticked by default. Tick it only if you want those actions. Each action asks you to confirm first.
Choose Allow to finish. See the privacy policy and terms for how VH3 handles your data. You can disconnect VH3 AI in Claude’s connector settings at any time. To change your choice, disconnect and connect again.

Try it

Ask Claude:
  • “How many jobs did we complete last week, broken down by engineer?”
  • “Which sites have had repeat visits this month?”
  • “Who could take job 12345 this week?”
Claude calls Job metrics for the first question and shows a chart in the chat. For the third, it calls Who could take a job, and when and lists engineers with times.

What you’ll see in Claude

In claude.ai and Claude Desktop, many answers open as a card you can use in the chat. Claude Code shows the same answers as text.

For test customers and early access

You can connect today, before the listing in the Claude directory goes live.
  • claude.ai, Claude Desktop or mobile: open Customize → Connectors, choose Add custom connector, and enter https://mcp.vh3.ai/mcp. Then sign in with your VH3 account.
  • Claude Code: run claude mcp add --transport http vh3-ai https://mcp.vh3.ai/mcp, or install the plugin above.
On Team and Enterprise plans, an Owner may need to allow custom connectors first. Tell your VH3 contact if a tool returns a “not found” error, because a few tools switch on as each release rolls out.

Available tools

Once connected, Claude can use these tools. They need no company_id or api_key, because your sign-in identifies your company.

Jobs and sites

Quotes and invoices

Reports and Ask Connie are switching on in stages. Generate operational report (reports_generate) and Ask Connie (can take actions) (connie_chat) appear in the list when they are live for your company. Connie through this connector sends email, SMS and notifications. It does not place voice calls.
investigate, the totals tools and scheduling_suggestions can take a while on large periods. If Claude reports that a call took too long, narrow the period or the question and ask again.

Troubleshooting a Claude connection

”Add custom connector” is missing

Your plan or organisation settings may not allow custom connectors. On Team and Enterprise plans, ask an owner to add the connector in Organization settings → Connectors.

Sign-in opens, but Claude shows an error afterwards

Disconnect VH3 AI in Claude’s connector settings and connect again. The connector URL is exactly https://mcp.vh3.ai/mcp, with no trailing slash and no path after mcp.

VH3 tools disappear after working for a while

Your VH3 account may have been archived, or your sign-in expired after a long period of no use. Connect again. If sign-in then fails with a message, see the table above.

Connie is missing from the tool list

Disconnect and connect again, and tick Allow actions on the consent page. Connie also appears only once it is live for your company.

Your organisation blocks the connection

Ask your IT team to allow outbound HTTPS to mcp.vh3.ai.

Advanced: developer access

Developers can connect Cursor, Claude Code, n8n and custom agents directly with a Bearer token. This path needs no OAuth sign-in. It talks to the VH3 MCP server at api.vh3connect.io, and it works for tools such as Claude Desktop that read a local config file.
Most Claude users should use Connect in Claude. The direct server also lists jobs_feed (an alias for list_jobs), and it lists reports_generate and connie_chat ahead of the connector.

Server details

If an existing client config still uses a URL ending /mcp/sse, change it to /mcp/stream and fully restart the client. Your JWT is unchanged.

Prerequisites

Claude Desktop and Cursor connect to remote MCP servers via a lightweight proxy called mcp-remote. It runs automatically through npx, which ships with Node.js.
1

Install Node.js (if not already installed)

Download the LTS installer for your platform from nodejs.org:
  • macOS: Download the .pkg installer from nodejs.org, open it, and click through the wizard. No terminal required.
  • Windows: Download the .msi installer. Make sure “Add to PATH” is checked during installation (this is the default).
After installing, verify by opening a terminal (macOS: Terminal.app, Windows: Command Prompt) and running:
Both should return a version number (e.g. v22.x.x). If npx is not recognised, Node.js is either not installed or not in your system PATH — see Troubleshooting developer access below.
2

Confirm your IT policy allows outbound HTTPS

The MCP proxy makes outbound HTTPS connections to api.vh3connect.io and registry.npmjs.org (to fetch mcp-remote on first use). If your organisation uses a firewall or proxy, ask your IT team to allowlist these domains.
Why Node.js? Claude Desktop’s config file launches local (stdio) MCP processes. The mcp-remote proxy runs locally and opens the HTTPS connection to VH3. This is the standard pattern recommended by the MCP specification.

Get your MCP token

Before connecting any client, you need a long-lived MCP token (valid for 90 days).
1

Log in to get a session JWT

Call the login endpoint with your email and password to obtain a standard session token:
Copy the authToken from the response.
2

Exchange it for an MCP token

Call the auth/mcp-token endpoint using your session token:
The response contains authToken (your 90-day MCP token) and expires_in: 7776000.
3

Store the token securely

Save the MCP token in an environment variable. Never commit it to source control.

Quick start: Claude Desktop

Claude Desktop connects to the VH3 MCP server using the mcp-remote proxy. Requires Node.js 18+.
1

Open your Claude Desktop config file

The config file location depends on your platform:You can also open it from Claude Desktop: Settings → Developer → Edit Config.Create the file if it does not exist.
2

Add the VH3 server

macOS:
claude_desktop_config.json
Windows:
claude_desktop_config.json
Replace YOUR_MCP_TOKEN with the token from Get your MCP token.
3

Restart Claude Desktop

Quit fully (Cmd+Q on macOS, File → Quit on Windows — closing the window is not enough) and reopen. You should see a hammer icon in the chat input. Click it to confirm the VH3 tools are listed.
4

Test with a query

Try: “How many jobs did we complete last week, broken down by engineer?”Claude will call aggregate_jobs and return a cited answer.
Windows users: You must use "command": "cmd" with "/c" as the first arg. Claude Desktop spawns the command directly without a shell, so npx alone will fail with spawn npx ENOENT. Wrapping it in cmd /c ensures Windows resolves npx via the system PATH.
The auth token is placed in the env block rather than inline in args. This is the recommended pattern — mcp-remote can misparse header values containing spaces when they appear directly in the args array on Windows.

Quick start: Cursor

Go to Cursor Settings → MCP and add a new server, or edit .cursor/mcp.json in your project root. Requires Node.js 18+. macOS:
.cursor/mcp.json
Windows:
.cursor/mcp.json
Replace YOUR_MCP_TOKEN with your token. See Get your MCP token.
Prefer environment variables over inline tokens. Set VH3_MCP_TOKEN in your shell profile and reference it from the config, or use Cursor Rules alongside the MCP connection to keep tokens out of config files.

Quick start: Claude Code

Claude Code connects over Streamable HTTP with your Bearer token and needs no Node.js proxy. See Get your MCP token first.
To skip the token, use the plugin or custom connector under Connect in Claude.

Quick start: n8n

Add an MCP Client Tool node with the endpoint https://api.vh3connect.io/x2/mcp/UZkEeuG7/mcp/stream, the HTTP Streamable transport, and a Bearer credential holding your MCP token. To build workflows without MCP, use the VH3 AI n8n node.

Authentication

The MCP server uses JWT Bearer token authentication. Tokens are obtained via the auth/mcp-token endpoint (see Get your MCP token above). The JWT encodes your user identity. All tool calls are automatically scoped to your company, no company_id or api_key parameters are needed. Cross-tenant access is impossible.
Never commit your MCP token to source control. Use environment variables and reference them from your MCP client configuration.

Troubleshooting developer access

spawn npx ENOENT (Windows)

Claude Desktop cannot find npx. Two possible causes:
  1. Node.js is not installed. Install it from nodejs.org and restart Claude Desktop.
  2. Node.js is installed but not in Claude Desktop’s PATH. Use "command": "cmd" with "/c" as the first arg (see Windows config above). Alternatively, use the full path to npx: "command": "C:\\Program Files\\nodejs\\npx.cmd".

npx is not recognized (Windows)

Same root cause as above — Node.js is not on the system PATH. Install Node.js using the .msi installer (not the zip), which adds it to PATH automatically. After installing, restart Claude Desktop (or reboot) so it picks up the new PATH.

”Not valid MCP server configuration”

The config JSON is malformed. Common causes:
  • Trailing comma after the last entry in an object or array.
  • Two separate JSON objects instead of one (e.g. mcpServers and preferences in separate {} blocks — they must be siblings in a single root object).
  • Using "url" or "headers" keys — Claude Desktop does not support these. Use the command + mcp-remote pattern shown above.
Paste your config into jsonlint.com to validate the JSON syntax.

Tools don’t appear after restart

  • Verify you fully quit Claude Desktop (Cmd+Q / File → Quit), not just closed the window.
  • Check logs: Settings → Developer → Open Logs Folder and look for mcp-remote stderr output.
  • Verify your token hasn’t expired (90-day lifetime). Re-run the token exchange if needed.
  • Confirm outbound HTTPS to api.vh3connect.io and registry.npmjs.org is not blocked by a firewall.
  • Confirm the server URL ends /mcp/stream, not /mcp/sse.

Tool calls timeout

investigate, reports_generate, and connie_chat can take 10–17 seconds. Some clients have aggressive timeouts. Increase your client’s tool call timeout to at least 25 seconds. scheduling_suggestions can take up to 45 seconds, and a live invoice_summary or quote_summary up to 90 seconds.

Further reading

Using the MCP server from custom agents

For agents built with the Anthropic SDK, OpenAI Agents SDK, or similar frameworks:

Tool selection guide for agents

When your agent receives a free-form question and needs to decide which tool to call: For a full system prompt you can paste directly into your agent, see the Claude.ai Projects and n8n Agent Prompts kits, both include routing logic optimised for agent use.

Pairing with AGENTS.md

If you’re using the MCP server inside a Cursor or Claude Code session, pair it with the AGENTS.md file in your project root. The MCP server handles execution; AGENTS.md handles routing logic, field name correctness, and the rules around what IDs to expose to users.

MCP Server (this page)

Handles execution, connects the client to the actual API, manages auth, returns real data.

AGENTS.md

Handles reasoning, tells the agent which tool to call, which parameters to pass, and how to present results.