Protocol reference

Aroai MCP endpoint and protocol

Connect using the combined Streamable HTTP endpoint, discover workspace-permitted tools and review transport, auth and capability behavior.

Endpoint

Use the combined endpoint to discover available tools across enabled servers. New Zealand and Core server-specific paths are also available.

Streamable HTTP endpoints
https://mcp.aroai.com/v1
https://mcp.aroai.com/v1/core
https://mcp.aroai.com/v1/nz

Transport and authentication

Aroai serves stateless Streamable HTTP. Clients can use OAuth where supported or a bearer API key. There is no SSE endpoint; clients should not use an SSE transport configuration.

Discover permitted tools

Tool listing reflects the selected workspace, enabled tools, active catalog state and client-supported features. Runtime discovery is authoritative for a connected workspace; this public catalog helps you understand documented capabilities.

Optional server filters

Server query filters can narrow the visible set of tools, for example by feature, explicit tool name or read-only mode. Client compatibility and permission enforcement remain distinct from schema annotations.

Results and executions

Responses include a concise text summary and structured data. Tool calls are recorded as executions; supported results can be fetched later using the workspace-scoped execution identifier.

Tools, resources, prompts and skills

These are distinct protocol features. Client support differs. The New Zealand company due diligence skill is published through resource/prompt delivery; reading a skill file alone does not activate it in every host.

Local intelligence. Ready to build.

Start with a task you can inspect.

Connect a compatible client, choose a workflow and review the source fields that come back.