Skip to main content
Kiwi provides a hosted Streamable HTTP MCP connection at the path /mcp. The signed-in app’s setup helper gives you the complete canonical endpoint for your project. OAuth protected-resource metadata is available at /.well-known/oauth-protected-resource/mcp on the same host. Use the endpoint from the helper; do not guess or type a host. For the default setup path, select the intended organization in Kiwi, then open Set up your agent → Copy setup prompt from Projects home or the global MCP & access page. Choose the project inside the helper. See Set up your agent for account, invitation, and client-connection steps.

Connect with OAuth

OAuth is the usual setup for an existing agent client. In that client’s MCP settings, add a remote server with the URL copied from Kiwi’s setup helper and use OAuth sign-in. The access token must target the exact /mcp resource and include the user:org:read scope. Select the organization that contains the intended project in the sign-in flow. Use the configuration controls supported by your agent client. If the client stores MCP settings in a file, follow that client’s own instructions and keep credentials in its credential store. The agent client connects directly to the hosted endpoint.

Project-bound MCP keys

For a client that supports a static Authorization header, a project Admin can open MCP & access, select one project, choose read-only or workflow-write access, and issue an expiring key. Send its one-time secret as a Bearer token:
Read-only keys can call read tools. Workflow-write keys can also start runs and report ordinary agent step progress. Both are restricted to one project and the issuer’s current project grant. They cannot make human decisions, manage organization settings, or submit checker-origin results. A checker key cannot authenticate to MCP. The key secret is returned only once. Issuance replay does not reveal it again or create a replacement. If the one-time secret is lost, revoke that key in Kiwi and issue a new one.

Available tools

Discover the current tool list in your MCP client after connecting. The hosted service supports these tools; argument names are camelCase. For workflow-skill versions, assignment instructions, and remote checks, see Workflow skills and execution records. For the step order, output shape, human pauses, and retry rules, follow the Agent guide. For CI check reports, use a checker credential and CI reporting.

MCP responses and errors

Successful tool calls return structuredContent as well as a text content item containing the same JSON. A run mutation returns an updated run projection and receipt. get_run returns a run projection and eventCursor; it does not return a full event list. The receipt identifies the command, whether it was recorded or replayed, the new run version and cursor, and the recorded event. A simplified get_run response has this shape:
Identifiers and versions above are illustrative. MCP errors return isError: true and a JSON text content item with error and message. If a mutation may have reached Kiwi but its response is missing, retry the identical command with the same payload. A successful MCP tool call does not establish acceptance of a workflow step or run.