Use an MCP API key for AI clients that do not support OAuth.
ChatGPT and Claude connect to Inrconnect through OAuth - you click "Sign in" and authorize the connection in your browser. Many other MCP clients (coding agents, CLI tools, custom applications) do not support OAuth. For those, Inrconnect supports MCP API keys.
An MCP API key is scoped to one organization and one integration, can be read-only or read-write, and can have individual tools disabled. You can revoke a key at any time without affecting your other connections.
MCP API keys are created per integration, so connect Housecall Pro or Jobber to your organization first.
In the Inrconnect dashboard, go to Organization > Integrations, open your connected integration, and switch to the MCP tab.
In the MCP API keys card, create a new key:
The key starts with mcp_live_ and is shown only once - copy it and
store it somewhere safe. If you lose it, revoke the key and create a new
one.
All Inrconnect MCP endpoints use the streamable HTTP transport and are reachable over the public internet:
| Integration | MCP endpoint |
|---|---|
| Housecall Pro | https://mcp.inrconnect.com/housecall-pro/mcp |
| Jobber | https://mcp.inrconnect.com/jobber/mcp |
Authenticate by sending your API key in the x-api-key request header:
x-api-key: mcp_live_your_key_hereUse the x-api-key header
Do not send the API key as a Bearer token in the Authorization header -
that header is reserved for OAuth tokens. API keys are only accepted in the
x-api-key header.
Use the endpoint that matches the integration the key was created for - a Housecall Pro key only works on the Housecall Pro endpoint.
See Client Configuration Examples for copy-paste configuration for Claude Code, Codex, Cursor, VS Code, Windsurf, and any other streamable HTTP client.
Email support@inrconnect.com and we will be happy to assist.