Export MCP and API configuration

What you can export

None of these exports contain secrets.

Add Nexra to an MCP client

Clients that support MCP authorisation need only the URL; they handle sign-in and token refresh themselves (see Authentication):

{
  "mcpServers": {
    "nexra": {
      "url": "https://api.nexra.amakoragroup.com/mcp"
    }
  }
}

For a client without OAuth support, or a server-to-server agent, exchange a credential for an access token at /oauth/token with the client_credentials grant and send it as a header:

{
  "mcpServers": {
    "nexra": {
      "url": "https://api.nexra.amakoragroup.com/mcp",
      "headers": {
        "Authorization": "Bearer ${NEXRA_MCP_TOKEN}"
      }
    }
  }
}

Keep tokens and credential secrets in your client's secret store or environment, never in a file you commit. Access tokens expire after an hour. Clients that only launch local (stdio) servers need a bridge that forwards to a remote HTTP server; Nexra does not ship a stdio package.

Export an integration as a service contract

The file nexra-connect-service.json has format: "nexra-connect-service-v1" and includes:

Each export is recorded in the workspace audit log as connect.integration.exported.

The export panel guides you through Review and activate → Set up application access → Connect and monitor. Downloading does not approve a flow or grant application access. Publish and independently review a production flow, activate its approved revision, and publish the Connect tools in an active application belonging to the same project. Sandbox flows remain available for tests in Nexra.

In the downloaded configuration, NEXRA_APPLICATION_TOKEN means the short-lived OAuth access token. It is not the raw MCP credential secret or your console sign-in token. For backend services, exchange the MCP credential prefix and secret at /oauth/token with grant_type=client_credentials, and renew the access token when it expires. Interactive OAuth clients can use the MCP endpoint and sign in instead. See authentication setup.

Invoking an exported integration

{
  "jsonrpc": "2.0",
  "id": 7,
  "method": "tools/call",
  "params": {
    "name": "trigger_approved_connect_integration",
    "arguments": {
      "integrationId": "<integration-id>",
      "idempotencyKey": "po-2026-10-07-0042",
      "correlationId": "agent-po-0042"
    }
  }
}

Follow the result with get_connect_integration_event, using the same integrationId and idempotencyKey. Only flows with an approved production deployment run.

Export API artefacts

For any published API product you can download:

curl -OJ "https://api.nexra.amakoragroup.com/api/developer-portal/public/catalogue/integration-sandbox/artifacts/openapi"

Add ?version=<version> to pin a version. See SDKs for the managed, versioned SDK pipeline.