How to give Claude access to your team’s projects and calls

Claude can work with your team’s project records when you connect it to your Starlings workspace over MCP. It acts as the member who pairs it: it can read what that person can read, and it can write only when that person grants write access.

This is a personal connection for a member’s Claude. A shared agent that appears in Team has its own identity and setup. If you want an agent teammates can address together, see [how to connect an agent as a Team member](/help/howto/connect-an-agent-as-a-team-member).

Connect Claude

1. In claude.ai or Claude Desktop, open Settings → Connectors → Add custom connector. Use your workspace’s MCP address: <your workspace origin>/mcp.
2. In Claude Code, add the same address with:

   claude mcp add --transport http --scope user starlings <your workspace origin>/mcp

   Then open /mcp in a Claude Code session, choose starlings, and authenticate.

3. Claude opens your workspace’s /connect page. Sign in as yourself and allow the connection. Leave Also write unchecked for a read-only start. Tick it only if you want Claude’s available write tools, such as creating a project task, and you are comfortable approving those actions through Claude.

Use the origin of the workspace where the project lives. Each workspace has its own /mcp address and connector. The [Claude setup guide](/help/howto/connect-claude) has the current client-specific steps.

What Claude can see

The connection follows your access. It can search and open project subjects, conversations, documents, tasks and issues that you can read. It can also read finalized meeting notes and transcript text when you hosted the meeting or when it is filed on a subject you can access. An unfiled meeting stays visible only to its owner.

It cannot read a live meeting, join a room, or access audio or video. Starlings does not record the audio or video of its calls. Claude’s meeting context begins with the finalized text artifact after the meeting ends.

Text that Claude reads from the workspace is sent to Anthropic under your own Claude account. Pair only the client you intend to use, and check that the relevant project and meeting records are ones you are allowed to share with that service. You can pause or revoke the connection from Settings → Account → Connected agents.

Start with a read-only question

Try a question about one project whose history you already know. Ask Claude to search for the project, open the relevant records, and show where its answer came from. For example, you might ask it to summarize decisions from a finalized call filed on that project and list the open tasks alongside them.

Then check the answer against the sources. If it cannot find a meeting or task, first check that the record is filed on the project and visible to your account. A title alone does not make an unfiled transcript available to another member.

Read access is enough for research, summaries and drafts in Claude’s conversation. When you decide to allow writes, pair again with Also write enabled. Claude can then use the write tools offered for your workspace, within your own permissions. Starlings records each call under your account and the client name; written work is attributed to you and marked with the client that made it.

For a first reviewed workflow, see [what a small consultancy should automate first](/field-notes/what-small-consultancies-should-automate-first). For the broader case for keeping an agent’s request and result with its project, read [why agents belong in the same project](/field-notes/why-agents-belong-in-the-same-project).