Connect an MCP client

All clients connect to the same origin-root Streamable HTTP endpoint and discover the same authorized tool catalog.

Prerequisites

• An Inttegro application
• A restricted Inttegro API key generated for that application
• An MCP client that supports remote Streamable HTTP and bearer authentication
• MCP form elicitation support if the client will perform confirmed actions

Store the key in the client's encrypted credential store or an environment variable named INTTEGRO_API_KEY. Never paste it into a prompt, commit it, expose it in browser code, or share it between unrelated applications.

Client configuration

Insomnia

Open Inttegro MCP in Insomnia, or create an MCP client using:

https://mcp.inttegro.com

In Auth, select Bearer Token and enter the raw Inttegro API key. Insomnia adds the Bearer prefix. Click Connect, then Resync after a server catalog change. A successful connection discovers 34 business tools.

Use a private Insomnia environment or approved credential store. Do not save the key in a Git-synced project.

Codex

Export the credential in the environment that launches Codex:

export INTTEGRO_API_KEY=<SECRET_KEY_TOKEN>

Add the server to your Codex configuration:

[mcp_servers.inttegro]
url = "https://mcp.inttegro.com"
bearer_token_env_var = "INTTEGRO_API_KEY"

Restart or reload Codex, then ask it to list the available Inttegro tools. See the official Codex MCP configuration for configuration-file locations and client controls.

Claude Code

Export the credential, then add this entry to .mcp.json at your project root:

{
  "mcpServers": {
    "inttegro": {
      "type": "http",
      "url": "https://mcp.inttegro.com",
      "headers": {
	"Authorization": "Bearer ${INTTEGRO_API_KEY}"
      }
    }
  }
}

Approve the project configuration when Claude Code asks you to trust it. Run claude mcp get inttegro or open /mcp to inspect the connection. Keep the real key in the environment, not in .mcp.json.

For the richer Inttegro Claude Code experience, see Use the Claude Code plugin.

Cursor

Export the credential, then add this entry to .cursor/mcp.json for the project or to your personal MCP configuration:

{
  "mcpServers": {
    "inttegro": {
      "url": "https://mcp.inttegro.com",
      "headers": {
	"Authorization": "Bearer ${env:INTTEGRO_API_KEY}"
      }
    }
  }
}

For cloud agents, enter the URL and bearer header through Cursor's MCP settings so the credential remains encrypted and outside the repository.

Other clients

Use these settings in any client that supports remote Streamable HTTP and custom headers:

Name: inttegro
URL: https://mcp.inttegro.com
Authorization: Bearer <SECRET_KEY_TOKEN>

Environment-variable syntax is not standardized. Use the client's documented secret facility and verify that it sends the header only to the exact origin above.

OpenAI and Anthropic API connectors

Applications using the OpenAI Responses API can provide the server URL as server_url and the restricted Inttegro key as authorization. Limit allowed_tools to the request and keep approval enabled for consequential calls. See OpenAI's remote MCP guide.

Applications using Anthropic's MCP connector can provide the same URL and key from their server-side secret store. The application—not the model or browser—owns acquiring, storing, and rotating that credential.

Verify the connection

1. Connect or resync the server.
2. Confirm the client discovers 34 business tools.
3. Call a narrow read such as list_products with a small limit.
4. Confirm the result belongs to the expected Inttegro application.
5. Before enabling actions, verify the client can display MCP form elicitation and require visible merchant confirmation.

If a client cannot carry form elicitation safely, keep the connection read-only. Do not replace server confirmation with model-generated approval text.

Troubleshoot

Symptom	Check
401 Unauthorized	The bearer token is present, current, restricted to the expected application, and sent to https://mcp.inttegro.com
No tools appear	The client supports remote Streamable HTTP; reconnect or resync after configuration changes
Reads work but actions fail	The client supports MCP form elicitation and the key has the required action scopes
OAuth sign-in does not start	The live protected-resource metadata must advertise an authorization server; use the direct API-key path for an intentional customer-controlled workload
A cloud agent cannot connect	Its execution region can reach the origin and its MCP settings—not repository files—contain the secret header

Next, review the tool catalog or try the merchant workflows.