Skip to content

Scopes

Not built yet. These scopes belong to a connector that is being built now. Nothing on this page works today (D0017).

A scope is one area of Team Cora that you let your AI client reach. Your AI client asks for scopes when it signs in, and you decide which it gets by how you set it up: Claude asks for more only when it needs them and you reconnect, and Claude Code asks for the list you pin. Team Cora’s sign-in page does not list the scopes.

A scope is your permission for the AI client, not a right. Your role still decides what you may do inside each area, exactly as in the console. Granting people.admin does not let a member change anyone’s role, because a member cannot do that in the console either (D0914).

Your AI client sees only the tools its scopes allow. On a first connection it sees the tools for reading missions and taking part, not the whole list (D0924).

Scope What it allows When it is asked for
missions.read Reading your organisations and missions, the mission chat, files, memory, heroes, members and notifications On first connect
missions.write Posting in a mission, answering questions, choosing on choice cards, and marking things read On first connect
missions.admin Setting up and managing missions: creating them, their settings, members, skills, memory, web access, schedules and the names of vault keys (never their values) When needed
heroes.write Making, changing and switching heroes, and adding a hero to a mission When needed
people.invite Inviting people to your organisation, and resending or cancelling invitations When needed
people.admin Changing people’s roles in the organisation, removing members, and the list of roles When needed
connections.read Listing your organisation’s connections and their tools When needed
connections.write Adding, changing, sharing and removing connections, and setting what each tool may do When needed
approvals.decide Approving or rejecting approval cards, and skill and team proposals When needed
org.admin Your organisation’s settings, writing to the team folder, sign-in apps for connections, and viewing billing When needed
profile.write Your own profile When needed

In full, each scope is the server’s address followed by its name, for example https://app.teamcora.ai/mcp/missions.read. Some sign-in screens show it that way.

The first release covers reading missions, taking part and setting up missions. Heroes, people, connections and approvals follow in a later release (D0929).

Some steps never happen through an AI client, whatever its scopes: typing a key or a password, paying, and signing in to another service. For those, your AI client gives you a link to finish in the console.

  • Claude (web, desktop and mobile) asks for a scope when it first needs one. If you ask Claude to set up a mission, Team Cora tells Claude that missions.admin is needed, and Claude asks you to connect again; signing in again gives it that scope (D0925). If you do not want it to have that scope, do not reconnect.
  • Claude Code does not ask on its own. It asks only for the scopes you pin when you add Team Cora. Use the command below.

Run this once, with your copied client ID in place of <client ID for Claude Code> (see Use Team Cora from Claude Code for where to copy it). If you already added Team Cora, sign out and remove it first, in this order: claude mcp logout team-cora, then claude mcp remove team-cora.

Terminal window
claude mcp add-json team-cora --scope user '{"type":"http","url":"https://app.teamcora.ai/mcp","oauth":{"clientId":"<client ID for Claude Code>","scopes":"https://app.teamcora.ai/mcp/missions.read https://app.teamcora.ai/mcp/missions.write https://app.teamcora.ai/mcp/missions.admin https://app.teamcora.ai/mcp/heroes.write https://app.teamcora.ai/mcp/people.invite https://app.teamcora.ai/mcp/people.admin https://app.teamcora.ai/mcp/connections.read https://app.teamcora.ai/mcp/connections.write https://app.teamcora.ai/mcp/approvals.decide https://app.teamcora.ai/mcp/org.admin https://app.teamcora.ai/mcp/profile.write"}}'

This pins every scope. To give Claude Code less, delete the addresses you do not want from the list; keep missions.read and missions.write. Then sign in with /mcp in Claude Code, or claude mcp login team-cora.

In Claude, disconnect Team Cora and connect again. It then starts again with only missions.read and missions.write, and asks for more only when you reconnect for a step that needs one.

In Claude Code, first run claude mcp logout team-cora, then claude mcp remove team-cora, then run the command again with a shorter list. Without the logout, the earlier sign-in, with its wider scopes, stays valid for up to 30 days.

Decisions: D0017, D0914, D0924, D0925, D0929.