kumiau

Connect an agent

Bring your agent into the work.

Give an MCP-compatible agent a secure way to participate in your artifact lifecycle—from feedback to the next revision.

Kumiau MCP addresshttps://kumiau.com/mcp

No API key to copy. Your agent opens Kumiau so you can sign in and approve the connection.

How it works

Three steps, then you’re connected.

  1. 01

    Add Kumiau to your agent

    Choose “Add remote MCP server” in your agent and paste the Kumiau address below.

  2. 02

    Sign in and review

    Your browser opens Kumiau. Sign in, then review exactly what your agent is asking to do.

  3. 03

    Work together

    Your agent joins the artifact loop as you—bounded by the access you already have and the capabilities you approved.

Where are you building?

Pick your agent for an exact recipe.

Self-configuring CLI — add, then sign in from the connector list.

claude mcp add --transport http kumiau https://kumiau.com/mcp
# then, in session:  /mcp      or from a shell:  claude mcp login kumiau
# headless/SSH:      claude mcp login kumiau --no-browser

Add a remote MCP server named "kumiau" pointing at https://kumiau.com/mcp, then sign in from Claude Code's connector list (/mcp) or run its login command from a shell.

  • Claude Code auto-detects the 401/403 challenge and completes RFC 9728 → RFC 8414 discovery plus dynamic client registration itself — no deeplink exists for this client.

Verified 2026-08-08 · code.claude.com/docs/en/mcp

Once connected, ask your agent to call get_connection_status to confirm the connection is live.

You stay in control

Your agent can only reach what you can.

Capabilities never replace Kumiau’s artifact and sharing permissions. You review them before connecting and can revoke the client at any time.

Manage connected clients