Client Configuration Examples

Before You Start

Every example below needs two things:

1. An MCP API key - see Connect with an API Key to generate one.
2. The endpoint for your integration:
   • Housecall Pro: https://www.inrconnect.com/housecall-pro/mcp
   • Jobber: https://www.inrconnect.com/jobber/mcp

The examples use the Housecall Pro endpoint - swap in the Jobber endpoint if that is the integration your key belongs to. Replace mcp_live_your_key_here with your actual API key everywhere it appears.

Claude Code

Add the server with one CLI command:

claude mcp add --transport http housecall-pro \
  https://www.inrconnect.com/housecall-pro/mcp \
  --header "x-api-key: mcp_live_your_key_here"

Or configure it in JSON - project-scoped in .mcp.json at your repo root, or user-scoped via claude mcp add --scope user:

{
	"mcpServers": {
		"housecall-pro": {
			"type": "http",
			"url": "https://www.inrconnect.com/housecall-pro/mcp",
			"headers": {
				"x-api-key": "mcp_live_your_key_here"
			}
		}
	}
}

Run /mcp inside Claude Code to confirm the server is connected.

Codex

Codex configuration lives in TOML at ~/.codex/config.toml (or project-scoped in .codex/config.toml):

[mcp_servers.housecall-pro]
url = "https://www.inrconnect.com/housecall-pro/mcp"
http_headers = { "x-api-key" = "mcp_live_your_key_here" }

Codex picks the transport from the keys you set - url means streamable HTTP. Run /mcp inside a Codex session to verify the connection.

Cursor

Add the server to .cursor/mcp.json in your project, or ~/.cursor/mcp.json to make it available everywhere:

{
	"mcpServers": {
		"housecall-pro": {
			"url": "https://www.inrconnect.com/housecall-pro/mcp",
			"headers": {
				"x-api-key": "mcp_live_your_key_here"
			}
		}
	}
}

To keep the key out of the config file, Cursor supports environment variable references: "x-api-key": "${env:INRCONNECT_MCP_KEY}".

VS Code (GitHub Copilot)

Add the server to .vscode/mcp.json in your workspace:

{
	"servers": {
		"housecall-pro": {
			"type": "http",
			"url": "https://www.inrconnect.com/housecall-pro/mcp",
			"headers": {
				"x-api-key": "mcp_live_your_key_here"
			}
		}
	}
}

Note that VS Code uses a top-level servers key rather than mcpServers.

Windsurf

Add the server to ~/.codeium/windsurf/mcp_config.json:

{
	"mcpServers": {
		"housecall-pro": {
			"serverUrl": "https://www.inrconnect.com/housecall-pro/mcp",
			"headers": {
				"x-api-key": "mcp_live_your_key_here"
			}
		}
	}
}

Windsurf also supports ${env:VAR_NAME} interpolation in headers if you prefer to keep the key in an environment variable.

Any Other Client

Inrconnect works with any MCP client that supports the streamable HTTP transport and custom request headers. Configure it with:

• URL / endpoint: the provider endpoint from the table above
• Transport: streamable HTTP (sometimes labeled "HTTP" or "remote")
• Header: x-api-key: mcp_live_your_key_here

If your client only supports OAuth or cannot send custom headers, use the ChatGPT or Claude style OAuth flow instead, or email us and we will help you get connected.

Verify the Connection

After adding the server, ask the client something narrow, like:

Search Housecall Pro for a customer named Smith.

If the client lists the Inrconnect tools and returns results, you are connected. Tool calls respect the key's access mode and any per-tool restrictions you configured.

Need Help?

Email support@inrconnect.com and we will be happy to assist.