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 merchant account and organization for interactive OAuth, or a restricted Inttegro API key for a workload connection
• An MCP client that supports remote Streamable HTTP and bearer authentication
• MCP form elicitation support if the client will perform confirmed actions

Client configuration

Insomnia

Open 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 80 tools when analytics is configured.

ChatGPT

Desktop app

Use this first when ChatGPT exposes MCP server settings:

1. Open Settings, then MCP servers.
2. Select Add server.
3. Name the server inttegro.
4. Choose Streamable HTTP.
5. Enter https://mcp.inttegro.com as the server URL.
6. Choose Bearer token authentication.
7. Enter your Inttegro secret key token.
8. Save the server, restart ChatGPT, then type /mcp.

ChatGPT web

Use Plugins or workspace Apps when your workspace supports custom MCP apps. Direct Inttegro connector installation is not enabled yet. If ChatGPT asks for a remote server URL, use:

Name: inttegro
Server URL: https://mcp.inttegro.com
Authentication: Bearer token
Bearer token: <SECRET_KEY_TOKEN>

If the ChatGPT surface only supports published connectors or OAuth-only linking and Inttegro is not available there yet, use Codex, Cursor, or another remote MCP client.

Codex

Desktop app

Use the GUI setup first:

1. Open Settings, then MCP servers.
2. Select Add server.
3. Name the server inttegro.
4. Choose Streamable HTTP.
5. Enter https://mcp.inttegro.com as the server URL.
6. Choose Bearer token authentication.
7. Enter your Inttegro secret key token.
8. Save the server, restart Codex, then type /mcp.

The ChatGPT desktop app, Codex CLI, and IDE extension share Codex MCP configuration for the same host, so a server added in one client can be reused from the others.

CLI / config.toml

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

Add the pre-registered public OAuth client:

claude mcp add inttegro https://mcp.inttegro.com \
  --transport http \
  --client-id e5FLCFhTxXPvnPbc \
  --callback-port 54113

Open /mcp, choose inttegro, and complete sign-in and organization selection in the browser. Claude stores and refreshes the resulting token; no client secret or merchant API key is required.

Keep inttegro and the server URL immediately after mcp add. Claude's --header option accepts multiple values and can consume trailing positional arguments. Do not add an Authorization header to this OAuth connection: Claude disables OAuth fallback whenever that header is configured.

For an intentional static-token connection, use a separate command without the OAuth options:

export INTTEGRO_API_KEY='replace-with-a-restricted-token'

claude mcp add inttegro https://mcp.inttegro.com \
  --transport http \
  --header "Authorization: Bearer ${INTTEGRO_API_KEY}"

For an intentional headless workload instead, export a restricted key and 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 any workload 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 80 tools when analytics is configured.
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.

Turn the connection into an integration plan

After verifying the connection, let the MCP prepare the integration brief instead of collecting SDK, checkout, endpoint, and testing instructions manually:

Use design_integration to help me choose our server runtime, SDK approach, first workflow, and checkout experience. Then give my coding agent the exact initial operations, implementation steps, Studio links, and end-to-end tests.

The tool is read-only and does not accept an API key. See Design an integration for every choice, result field, and agent-handoff step.

Troubleshoot

Symptom	Check
OAuth sign-in does not open	The client uses ID e5FLCFhTxXPvnPbc, callback port 54113, and the exact server origin above
Claude treats inttegro as a header value	Put inttegro https://mcp.inttegro.com immediately after claude mcp add; --header is variadic
A static token fails and OAuth does not open	Remove the configured Authorization header before using the OAuth client; the two authentication modes must not be combined
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

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