MCP

Cette page n’est pas encore disponible en français. Vous consultez la version anglaise.

Service API runs an MCP server (Streamable HTTP transport, stateless — no session affinity required) at:

https://service.testing.nairon.cloud/mcp

Authenticate the same way as any other Service API request: Authorization: Bearer nrn_sk_....

Tools

The server exposes 41 tools today, and 42 with the next service release (adding get_context). Each tool is equivalent to one operation in Resources — see that page for request/response shapes and behavior.

Tool	Equivalent to
`get_organization`	`GET /v1/organization`
`get_context` (next service release)	`GET /v1/me` — the calling key’s organization id, project id, scope, and name
`get_usage`	`GET /v1/organization/usage`, `GET /v1/projects/{projectId}/usage`, `GET /v1/orgs/{orgId}/usage` — not available yet, returns an error with code `usage_unavailable`
`get_project`	`GET /v1/projects/{projectId}`
`get_agent`	`GET /v1/projects/{projectId}/agent`
`update_agent`	`PATCH /v1/projects/{projectId}/agent`
`get_simple_agent`	`GET /v1/projects/{projectId}/agent/simple`
`update_simple_agent`	`PUT /v1/projects/{projectId}/agent/simple`
`list_skill_catalogue`	`GET /v1/catalogue/skills`
`list_conversations`	`GET /v1/projects/{projectId}/conversations`
`create_conversation`	`POST /v1/projects/{projectId}/conversations`
`get_conversation`	`GET /v1/conversations/{id}`
`update_conversation`	`PATCH /v1/conversations/{id}`
`delete_conversation`	`DELETE /v1/conversations/{id}`
`get_conversation_design`	`GET /v1/conversations/{id}/design` (active version only)
`save_conversation_design`	`PUT /v1/conversations/{id}/design`
`list_conversation_versions`	`GET /v1/conversations/{id}/versions`
`activate_conversation_version`	`POST /v1/conversations/{id}/versions/{n}/activate`
`list_knowledge`	`GET /v1/projects/{projectId}/knowledge`
`create_knowledge`	`POST /v1/projects/{projectId}/knowledge`
`get_knowledge`	`GET /v1/knowledge/{kbId}`
`delete_knowledge`	`DELETE /v1/knowledge/{kbId}`
`create_knowledge_source`	`POST /v1/knowledge/{kbId}/sources`
`delete_knowledge_source`	`DELETE /v1/knowledge/{kbId}/sources/{id}`
`list_integrations`	`GET /v1/projects/{projectId}/integrations`
`list_numbers`	`GET /v1/projects/{projectId}/numbers`
`update_number`	`PATCH /v1/numbers/{id}`
`list_web_agents`	`GET /v1/projects/{projectId}/web-sessions/agents`
`create_web_agent`	`POST /v1/projects/{projectId}/web-sessions/agents`
`update_web_agent`	`PATCH /v1/projects/{projectId}/web-sessions/agents/{id}`
`delete_web_agent`	`DELETE /v1/projects/{projectId}/web-sessions/agents/{id}`
`create_web_session`	`POST /v1/web-sessions`
`list_keys`	`GET /v1/projects/{projectId}/keys`
`create_key`	`POST /v1/projects/{projectId}/keys`
`revoke_key`	`POST /v1/keys/{id}/revoke`
`query_knowledge_base`	Queries a knowledge base’s contents
`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}` (name, description, agent profile)
`save_flow_version`	`POST /v1/flows/{flowId}/versions` (saves and activates a new version)
`activate_flow_version`	`POST /v1/flow-versions/{versionId}/activate`

Default project (next service release). Every tool that takes a projectId will accept it as optional: leave it out and the tool uses your key’s own project (for get_usage, when neither projectId nor organizationId is given). A projectId of another project is still rejected with not_found. REST paths keep {projectId} in the path — read it from GET /v1/me.

The six *_flow* tools work on a project’s flows in the editor’s own format. For new integrations, prefer the Conversation tools and the portable Conversation Design.

get_conversation_design reads only the active version — list_conversation_versions covers version history; fetching one specific past version’s design is REST-only (GET /v1/conversations/{id}/versions/{n}/design).

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.testing.nairon.cloud/mcp with an Authorization: Bearer header

Or configure it as a remote MCP server in any client that supports custom servers, supplying the URL and your secret API key as a bearer token.

Also see

Resources — the operations each tool wraps.
Errors — errors use the same codes over MCP as over REST; a failed tool call returns an error result whose text is <message> (code: <code>, requestId: <id>).