# Starlings

> Meetings, calendar, work and team for Envisioning: a Mac app, an iOS app and a web app on one control plane. Members reach it through Claude over MCP at `/mcp`.

## Surfaces

- [surfaces/admin](https://meet.envisioning.workers.dev/help/surfaces/admin): Admin: the org in five destinations, including measured client-reported RTP data; members only
- [surfaces/calendar](https://meet.envisioning.workers.dev/help/surfaces/calendar): Calendar: Google, EventKit and subscriptions, one week or day or month; ⌘2; `/calendar`
- [surfaces/docs](https://meet.envisioning.workers.dev/help/surfaces/docs): Docs: the whole corpus, with a linked graph view; save links on iOS and Mac; ⌘5; `/docs`
- [surfaces/ended](https://meet.envisioning.workers.dev/help/surfaces/ended): Ended: the meeting is over, how long it lasted, why it ended
- [surfaces/home](https://meet.envisioning.workers.dev/help/surfaces/home): Home: the clock, the modules in your order, and your room. ⌘1; the first tab; `/`
- [surfaces/meeting](https://meet.envisioning.workers.dev/help/surfaces/meeting): Meeting: the stage, the rail and the control row while a call is live
- [surfaces/prejoin](https://meet.envisioning.workers.dev/help/surfaces/prejoin): Prejoin: before you join, the camera and microphone check, then Ask to join
- [surfaces/room-entry](https://meet.envisioning.workers.dev/help/surfaces/room-entry): Room entry: a guest at `/room/<slug>`, with a name, an email and two doors
- [surfaces/schedule](https://meet.envisioning.workers.dev/help/surfaces/schedule): Schedule: `/book/<slug>`, pick a time, say who you are
- [surfaces/search](https://meet.envisioning.workers.dev/help/surfaces/search): Search: the ⌘K palette, one box that finds anything and jumps anywhere
- [surfaces/settings](https://meet.envisioning.workers.dev/help/surfaces/settings): Settings: account, room policy, calendar, audio, video, captions, Home layout, Inbox sources, language; ⌘,; `/settings`
- [surfaces/team](https://meet.envisioning.workers.dev/help/surfaces/team): Team: who at Envisioning is around, and reaching them; ⌘4; `/team`
- [surfaces/waiting-room](https://meet.envisioning.workers.dev/help/surfaces/waiting-room): Waiting room: the knock is sent; the owner decides
- [surfaces/work](https://meet.envisioning.workers.dev/help/surfaces/work): Work: every subject, what needs you, what you owe; ⌘3; `/work`

## How-to

- [howto/answer-a-decision](https://meet.envisioning.workers.dev/help/howto/answer-a-decision): Answer the decisions an agent put to you, from INBOX on any client; how an agent asks and reads the answer
- [howto/book-a-time](https://meet.envisioning.workers.dev/help/howto/book-a-time): Find a time with a member at `/book/<slug>`
- [howto/call-a-colleague](https://meet.envisioning.workers.dev/help/howto/call-a-colleague): Wave for attention, or Call into their room
- [howto/connect-a-repository](https://meet.envisioning.workers.dev/help/howto/connect-a-repository): Map a GitHub repository to a project at `/admin/connectors/github`
- [howto/connect-claude](https://meet.envisioning.workers.dev/help/howto/connect-claude): Pair a Claude with Starlings over MCP at `/connect`
- [howto/file-a-task-on-github](https://meet.envisioning.workers.dev/help/howto/file-a-task-on-github): Turn a task into an issue on the subject's repository
- [howto/hand-off-a-card-to-an-agent](https://meet.envisioning.workers.dev/help/howto/hand-off-a-card-to-an-agent): Give a task or an issue to an agent from Work
- [howto/host-a-meeting](https://meet.envisioning.workers.dev/help/howto/host-a-meeting): Open your room, admit who knocks, end it; from the Mac, the phone, or the CLI
- [howto/join-a-room](https://meet.envisioning.workers.dev/help/howto/join-a-room): Enter a room as a guest: the link, your name and email, the check, the knock
- [howto/labels-the-board-reads](https://meet.envisioning.workers.dev/help/howto/labels-the-board-reads): Which GitHub labels move a card on the Work board, and which are inert
- [howto/message-a-colleague](https://meet.envisioning.workers.dev/help/howto/message-a-colleague): Send a message, start a group, or reach Everyone from Team
- [howto/read-a-meeting-transcript](https://meet.envisioning.workers.dev/help/howto/read-a-meeting-transcript): Find the transcript and notes of a meeting that ended
- [howto/read-project-status](https://meet.envisioning.workers.dev/help/howto/read-project-status): Have a Claude answer where a project stands: which read to make, the six stage words, and what a status is not
- [howto/remove-a-channel-without-a-subject](https://meet.envisioning.workers.dev/help/howto/remove-a-channel-without-a-subject): Remove a channel whose project, lead, partner or event was deleted in Core, and put it back (admins)

## Glossary

- [glossary](https://meet.envisioning.workers.dev/help/glossary): what each word means in Starlings, with its source

## Capabilities

- [features/status](https://meet.envisioning.workers.dev/features/status): every capability, where it works, and the door an agent has into it; the same rows are in llms-full.txt

## Agent access

- MCP endpoint: https://meet.envisioning.workers.dev/mcp
- Pairing: Only a member of this workspace can pair Claude. Starlings has no self-serve workspace yet. [How to connect Claude](https://meet.envisioning.workers.dev/help/howto/connect-claude).
- OpenAPI 3.1: https://meet.envisioning.workers.dev/openapi.json (the internal routes wrapped by MCP)
- Door grammar: things use `subject:<kind>:<id>`, `person:<email>`, `agent:<email>`, `thread:<id>`, `document:<id>`, `event:<id>`, `task:<id>`, `issue:<owner>/<repo>#<number>` or `core:<id>`; places use `destination:<home|calendar|work|team|docs>`, `settings:<account|home|work|calendar>` or `verb:<new-task|new-issue|new-document|start-room|open-internal-room>`. `open` accepts thing doors only.
- Agents never enter a room or read live meetings; they can read finalized artifacts after a meeting ends. Every MCP call is recorded.

### MCP tools

- search: Search everything the signed-in member can see in Starlings: subjects (leads, projects, partners, events), people, agents, conversations, documents, calendar events, tasks and GitHub issues.
- open: Open the thing behind a `door` from `search`.
- now: What is happening for the signed-in member right now: who is around, the next 24 hours of calendar, the latest activity across every subject, their own tasks and issues, their quick notes (`quick_notes`, open ones first: to triage one, pass its id as `quick_note` to `task`, `create_issue`, `send_message` or `docs_write`, which files it there), open decisions they asked or owe (`decisions_waiting`, overdue first) and those answered in the last week (`decisions_answered`).
- transcript: The finalized record of one meeting the member hosted: notes and transcript text.
- send_message: Send a message as the member into a conversation they are in.
- task: Create or change a task as the member, or create a new lead.
- record_decision: Record a decision on a subject, as the member: something the team settled, in one to a few sentences.
- ask_decision: Put a decision in the member's decision queue, and read the answers.
- set_goal: Create a goal on a project, or change one, as the member.
- create_issue: File a GitHub issue on a project's linked repository, as the member.
- schedule: Put an event on the member's Google Calendar, as the member.
- start_meeting: Schedule a meeting in the member's own Starlings room and ask one of their devices to open it.
- cms: Read or change records in Core: website content (CMS entities) and the CRM records `organizations`, `contacts`, `interactions`, `projects` and `leads`.
- docs_write: Create or update an Envisioning Docs document, as the member.

## Changelog

- [changelog](https://meet.envisioning.workers.dev/changelog.md): every release, newest first, as markdown; the page is https://meet.envisioning.workers.dev/changelog

Full text: https://meet.envisioning.workers.dev/llms-full.txt