Skip to main content

Native MCP Integration

Use native MCP integration when you want your own LLM client, agent framework, or backend service to connect to an InstaMCP integration without showing the hosted widget.

For website chat, use Installing the Widget instead.

When to Use This​

Use native MCP when:

  • Your application already has its own chat UI.
  • Your LLM or agent framework can connect to MCP over SSE.
  • You want to expose the tools attached to an integration directly to your LLM.
  • You need server-side control over how the LLM chooses and calls tools.

What You Need​

From the integration page, copy:

  • Product key.
  • Bridge instance ID, also shown as a deployment ID.
  • API base URL.

If the integration has more than one bridge instance enabled, send X-MCP-Deployment-Id so InstaMCP knows which bridge to route to.

Test the SSE Endpoint​

Use the cURL example shown in the integration page. It follows this shape:

curl -N \
  -H "Accept: text/event-stream" \
  -H "X-Product-Key: YOUR_PRODUCT_KEY" \
  -H "X-MCP-Deployment-Id: TARGET_DEPLOYMENT_ID" \
  -H "X-MCP-Auth-Token: YOUR_OPTIONAL_HOP_TOKEN" \
  "https://api.instamcp.digineuron.agency/api/v1/products/public/mcp/sse"

Use X-MCP-Auth-Token only when downstream tools require user-scoped auth.

Send MCP Messages​

The SSE handshake provides the upstream ?u=... value. Use that value with the messages endpoint.

curl -X POST \
  -H "Content-Type: application/json" \
  -H "X-Product-Key: YOUR_PRODUCT_KEY" \
  -H "X-MCP-Deployment-Id: TARGET_DEPLOYMENT_ID" \
  "https://api.instamcp.digineuron.agency/api/v1/products/public/mcp/messages?u=ENCODED_UPSTREAM_FROM_SSE" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list",
    "params": {}
  }'

Ask AI to Add It as MCP​

The integration page includes a copyable prompt you can paste into an AI coding agent. It gives the SSE URL and required headers so the agent can add the MCP server to your app or LLM client.

Authentication​

Always send X-Product-Key.

Send X-MCP-Auth-Token only when your downstream tools need per-user credentials. For more detail, see Double-Hop Authentication.

Troubleshooting​

  • If the connection fails, confirm the product key is current.
  • If tools are missing, confirm the bridge instance ID is enabled on the integration.
  • If the tool needs user credentials, confirm X-MCP-Auth-Token is present.
  • If the integration has multiple bridge instances, confirm X-MCP-Deployment-Id is present.