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/mcpAuthenticate the same way as any other service-api request: Authorization: Bearer nrn_sk_....
| Tool | Equivalent to |
|---|---|
list_flows | GET /v1/projects/{projectId}/flows |
get_flow | GET /v1/flows/{flowId} |
create_flow | POST /v1/projects/{projectId}/flows |
update_flow | PATCH /v1/flows/{flowId} |
save_flow_version | POST /v1/flows/{flowId}/versions |
activate_flow_version | POST /v1/flow-versions/{versionId}/activate |
query_knowledge_base | proxies platform-api’s POST /v1/stores/{id}/query |
get_usage | project + org usage timeseries |
Connecting
Section titled “Connecting”Any MCP client that supports a remote Streamable HTTP server can connect directly. For example, with the MCP Inspector:
npx @modelcontextprotocol/inspector# then connect to https://service.v2.nairon.xyz/mcp with an Authorization: Bearer headerOr 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.