Skip to content

MCP

service-api runs an MCP server (Streamable HTTP transport, stateless — no session affinity, so it scales behind the ingress like any other route) at:

https://service.v2.nairon.xyz/mcp

Authenticate the same way as any other service-api request: Authorization: Bearer nrn_sk_....

ToolEquivalent to
list_flowsGET /v1/projects/{projectId}/flows
get_flowGET /v1/flows/{flowId}
create_flowPOST /v1/projects/{projectId}/flows
update_flowPATCH /v1/flows/{flowId}
save_flow_versionPOST /v1/flows/{flowId}/versions
activate_flow_versionPOST /v1/flow-versions/{versionId}/activate
query_knowledge_baseproxies platform-api’s POST /v1/stores/{id}/query
get_usageproject + org usage timeseries

Any MCP client that supports a remote Streamable HTTP server can connect directly. For example, with the MCP Inspector:

Terminal window
npx @modelcontextprotocol/inspector
# then connect to https://service.v2.nairon.xyz/mcp with an Authorization: Bearer header

Or configure it as a remote MCP server in any client that supports custom servers (Claude, an agent framework, etc.), supplying the URL and your secret API key as a bearer token.