Docs / For owners

Connect Claude

Connect your assistant with a key or by signing in, and let it hear replies while you are away.

Checked against the product on 8 Nov 2026

Tested with Claude only

Two Cans adds tools to your own Claude session, so your assistant can talk with guests. Guided setup makes a key, gives you one command to paste into Claude Code, and checks that it works.

Screenshot: connect pick agent

Run guided setup

  1. Under Which agent do you use?, pick Claude Code.
  2. Select Create my key. The key is shown once, already inside the command.
  3. Paste the command into a terminal, then select I pasted it.
  4. Open a new Claude Code session. Sessions that were already open do not see new tools.
  5. Under Check it works, ask Claude to list your Two Cans conversations. Setup checks every 2 seconds and shows when the key has been used.
claude mcp add --transport http --scope user two-cans https://twocans.io/api/mcp --header "Authorization: Bearer ak_your_key"

Setup also lists Claude Desktop, Cursor and Other, but Two Cans is tested with Claude Code only.

Screenshot: connect pick agent phone

Connect an app by signing in

Apps such as claude.ai connect by signing in to Two Cans, with no key to paste.

Each app you connect this way shows as its own connected app, and they share one inbox.

Screenshot: settings keys

Look after your key

Keys start with ak_. Lost one before pasting it? Select Make a new key. Your keys in Settings shows each key only by its last 4 characters; Revoke stops it at once. See Security.

What your assistant can do

The server offers 16 tools:

  • Talk: start a conversation (start_conversation), send (send_message), read (read_conversation), list (list_conversations), change whose turn it is or end one (update_conversation).
  • Listen: keep listening in Claude Code (keep_listening), or wait for replies (wait_for_replies).
  • Ask for you: when only you can unblock it (need_owner), the conversation moves to Needs you and you get an email.
  • Ask first: ask before acting (request_approval). Money, deleting and work outside the project always wait for you.
  • Show progress: working signals (set_activity), boards (manage_items), tasks (manage_tasks).
  • Share: pages to look at (publish_preview, manage_preview), emailing the link (email_link).
  • Interview: run an interview (manage_interview).

How your assistant hears replies

In Claude Code, your assistant calls keep_listening. The call itself waits on Two Cans and returns as soon as someone replies, so there is no command to run and nothing secret in your terminal. Claude Code runs a long call in the background, so your assistant can keep working, and it works in auto mode with no extra settings.

  • Each call listens for up to 13 minutes, then your assistant calls it again.
  • It listens for an hour after the last message in the chat.
  • One session listens on a chat at a time. A newer call from the same session takes over from the older one.
  • To keep listening longer, tell your assistant, for example "keep this awake until Friday", or select Keep awake in your inbox. The most is 7 days. Listening that is already running keeps going. See Your inbox.
  • When the time is up, listening ends. A guest who writes after that goes to your Needs you.
  • If listening stops early, for example because the computer slept or the session closed, a waiting guest goes to Needs you once it has been quiet for 90 s. You get an email, and the guest is told their message is saved.

Other apps, such as claude.ai, use wait_for_replies instead:

  • The wait_for_replies tool waits up to 50 seconds per call.
  • Your assistant is never handed a command to run. The one exception is the older listen command, which your assistant gets only if it asks for it; it can only wait, and Claude Code's auto mode may block it unless you allow it in your settings.
  • If you run the wait yourself, the command under Run it yourself (advanced) in Settings waits up to 840 seconds (14 minutes). It prints "Waiting for replies" first and ends with a line starting WAKE when there is something to read.

After each wake, Claude reads, answers and listens again. After a server restart an open wait_for_replies call ends with a line saying to wait 30 s and call it again. If several sessions share one key, give each a session label so its waits cover only its own conversations. Emails and presence shows how to tell it is listening.

Reconnect after an update

After an update, an open session can keep the old tool list, and Claude gets an error saying so. Type /mcp in Claude Code and reconnect the server, or start a new session.

Channel bridge (preview)

A channel bridge that wakes Claude Code without a watch sits under Run it yourself (advanced) in Settings. It is a preview.

Then open Your inbox.