Skip to main content
Use the agent environment you already have. This setup connects it to one hosted Kiwi project and checks what it can read. It does not create a workflow, run, or code task. Paste this into your agent:

​
Choose your account path

  • New to Kiwi: create an account at Kiwi sign-up. First-time setup creates an organization and My first project.
  • Joining a team: accept the organization invitation, then open the project you were invited to use. Organization membership does not grant access to every project. If it is missing, ask a project Admin for access.
  • Already use Kiwi: select an organization in the app, then choose a project you can access inside the setup helper.
See Organizations and accounts for membership and role details. Complete sign-in, invitation acceptance, and any permission changes in Kiwi.

​
Copy the project’s setup prompt

In the signed-in app, select the intended organization. Open Set up your agent → Copy setup prompt from Projects home or the global MCP & access page. Choose the project inside the helper. If only one project is available, it is selected for you; otherwise, choose the intended project. Paste the copied prompt into your agent. It contains the canonical MCP endpoint and the selected organization’s and project’s names and IDs as JSON data. Those values identify the connection; they are not credentials. The prompt contains no access token, key, password, or secret. Ask your agent to add the connection through the MCP settings supported by that agent environment. Use the endpoint and selected project details from the copied prompt. Preserve other configured servers and ask before replacing a conflicting Kiwi entry. If your client stores MCP settings in a file, follow that client’s instructions. This connection uses Kiwi’s hosted service through OAuth. Complete sign-in in the client and select the organization that contains the project. No API key is required for OAuth. Verify the connection with actual MCP responses: call list_projects, match the exact project ID from the setup prompt, then call list_workflows for that project. Report what those calls returned. If the project is absent, access is denied, or the calls are unavailable, explain the next step and stop. Copying the prompt or seeing documentation does not prove an authenticated connection. Setup creates no workflow or run. MCP cannot publish a workflow, look up members, identify the current user with whoami, report a CI check, or make a human decision. If you later want a tracked task and the project has no published Development workflow, a project Admin must publish it in the Kiwi app first. The manual quickstart and workflow guide explain that path.

​
Optional: track a Development task

After connection is verified, use this only when you want a specific task tracked in Kiwi. Describe the task in plain language. Starting a run is a separate choice from setup.
An agent may submit a Plan when the run allows it, but the designated owner accepts it in the app. The reviewer makes Human acceptance in the app. An MCP tool receipt does not mean either decision passed. If a task needs a human-attested check and the agent cannot confirm a real eligible reporter, ask a project Admin to resolve the assignment; MCP has no member-lookup tool.

​
Optional: prepare team or CI setup

For team access, ask the agent to prepare steps from Organizations and accounts:
For CI, use Connections and CI reporting:
For a manual first run in the hosted app, see the quickstart. For exact agent actions in an existing run, use the Agent guide. For check results, see CI reporting.