Connect Claude

Only a member of this workspace can pair Claude. Starlings has no self-serve workspace yet. The pairing signs in as that member, and Claude reads only what the member can read.

The public Starlings site publishes the help pages; use your workspace address for pairing, including /connect and /mcp.

1. Add Starlings as a connector in Claude. Use the address <your Starlings origin>/mcp. The client registers itself.
   • claude.ai or Claude Desktop: Settings → Connectors → Add custom connector.
   • Claude Code: run claude mcp add --transport http --scope user meet <your Starlings origin>/mcp, then open /mcp in a claude session, choose meet and Authenticate.
2. The browser opens /connect. Sign in as yourself. To let Claude write, tick Also write before you allow the pairing. Without it, Claude only reads.
3. Claude now has these tools: search, open, now, transcript, schedule, start_meeting, send_message, task, create_issue, record_decision, ask_decision, set_goal, cms, docs_write. A read-only pairing lists only the read tools. ask_decision puts a question in your decision queue when you are not in the conversation (a background or scheduled run); while you are talking with Claude it asks you there. You answer it from INBOX (Answer a decision). task also creates a lead: pass action: "create_lead" and a title, and Claude gets the lead's door and its channel, where Core posts New Lead Created. Claude can also set a lead's five qualification checks, on create or later with update_lead. Claude cannot delete a lead. Claude reads your Quick Notes through now and files one by passing its id as quick_note to task, create_issue, send_message or docs_write; the note is marked filed there, as File… does. Claude cannot delete a note. Claude can merge duplicate contacts or organizations in Core with cms and merge: Core keeps the oldest, moves everything from the others onto it, and records the merge; Claude names the survivor to you first. Claude also gets the resources and prompts, and an index of the product at /llms.txt.
4. When Starlings refuses a call, or the call fails, Claude gets the reason and a suggested next step. Claude can tell you both. A read-only pairing refuses every write. To allow writes, Revoke the pairing and pair again with Also write ticked.
5. A message Claude sends with send_message is yours, and shows a quiet via claude.ai (or your client's name) beside the time, so the people reading it can tell.
6. Starlings records every call. See yours under Settings → Account → Connected Claudes, or all of them on Admin. Revoke ends the pairing.
7. Pause stops a Claude at its next call and keeps the pairing. Starlings refuses each call and tells Claude that you paused it. Resume lets the next call through. You do not pair again.

Have a Claude start a meeting

Ask Claude to start a meeting. Claude calls start_meeting. This puts the meeting on the calendar, in your own room, and asks your devices to open the room.

Each of your running clients shows Open room or Not now. You have 45 seconds to answer, the same limit as a Wave. The room opens only when you choose Open room. If you do not answer, the meeting stays on the calendar and the room stays closed.

Starlings transcribes a room opened this way, because it is a convened meeting with a title and attendees. Starlings does not transcribe a room opened from a colleague's Call.

For an ordinary calendar event, use schedule. It does not ask your devices and does not open a room.