Connect with an API Key
Use an MCP API key for AI clients that do not support OAuth.
Overview
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.
Generate an MCP API Key
Connect your integration first
MCP API keys are created per integration, so connect Housecall Pro or Jobber to your organization first.
Open the MCP tab
In the Inrconnect dashboard, go to Organization > Integrations, open your connected integration, and switch to the MCP tab.
Create the key
In the MCP API keys card, create a new key:
- Name it after the client that will use it (for example "Cursor" or "Codex"), so it is easy to identify and revoke later.
- Choose Read-only or Read-write access. Use read-only unless the client needs to create or change records.
- Optionally disable individual tools the client should not have.
Copy the 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.
Connection Details
All Inrconnect MCP endpoints use the streamable HTTP transport and are reachable over the public internet:
| Integration | MCP endpoint |
|---|---|
| Housecall Pro | https://www.inrconnect.com/housecall-pro/mcp |
| Jobber | https://www.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.
Configure Your Client
See Client Configuration Examples for copy-paste configuration for Claude Code, Codex, Cursor, VS Code, Windsurf, and any other streamable HTTP client.
Security Recommendations
- Create a separate key per client so you can revoke one without breaking the others.
- Default to read-only access; enable read-write only for workflows that need it.
- Store keys in environment variables or your client's secret storage instead of committing them to shared config files.
- Revoke keys you no longer use from the same MCP tab.
Need Help?
Email support@inrconnect.com and we will be happy to assist.