Export MCP and API configuration
Add Nexra to an MCP client, download an integration's service contract and export API artefacts.
Updated 07/10/2026
On this page
What you can export
| Export | Where | Contains |
|---|---|---|
| MCP client configuration | Dashboard → MCP → your app → Connection guide | The server URL and authorisation header to paste into an MCP client |
| Integration service contract | Connect → Integrations → your integration → Review API / MCP export | nexra-connect-service.json: flows, operations, mappings, invocation and monitoring details, and the MCP client block |
| OpenAPI, Postman and SDK files | API reference → Download, or the public artefact endpoint | Specifications and generated client code for a published API product |
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://ca-amakora-devportal-api-prod.salmonground-f19b34da.uksouth.azurecontainerapps.io/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://ca-amakora-devportal-api-prod.salmonground-f19b34da.uksouth.azurecontainerapps.io/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
Open the integration in Dashboard → Connect → Integrations. You can also export from the last step of the New integration wizard.
Choose Review API / MCP export and check the summary.
Choose Download service contract. The button is available once the integration has at least one flow.
The file nexra-connect-service.json has format: "nexra-connect-service-v1" and includes:
integration: name, project and owners.
flows: one entry per flow, with productionReady, the bound source and destination operations, the mapped field paths and an invoke template.
mcp: the endpoint path /mcp, the transport streamable-http, the credential scope (workspace-and-project), the five Connect tools and setup notes.
invoke: how to start the integration with trigger_approved_connect_integration.
monitor: how to follow an event with get_connect_integration_event.
mcpServers.nexraConnect: a ready-to-paste client entry using ${NEXRA_APPLICATION_TOKEN}.
runtime: "hosted-by-nexra": the integration keeps running in Nexra. The contract describes how to call it; it is not a deployable copy.
Each export is recorded in the workspace audit log as connect.integration.exported.
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:
| Format | File |
|---|---|
openapi | OpenAPI JSON |
postman | Postman collection JSON |
typescript, python, go, csharp, java | Generated client source |
curl -OJ "https://ca-amakora-devportal-api-prod.salmonground-f19b34da.uksouth.azurecontainerapps.io/api/developer-portal/public/catalogue/integration-sandbox/artifacts/openapi"Add ?version=<version> to pin a version. See SDKs for the managed, versioned SDK pipeline.