Crewshal
Sign in

Feature · Platform

Connections

Add Crewshal to Claude, ChatGPT, Claude Code or Codex. The model runs there on your plan and uses Crewshal's tools to read and assign work.

Last changed

Generated from commit a7a1a63 ·

Open Connections Code view for the platform team

How it works

Connect

  • Claude (web, desktop, mobile): Settings, Connectors, Add custom connector. Enter your Crewshal server's /mcp address. The connector address is on Connections.
  • Claude Code: claude mcp add --transport http agent <address>, then /mcp to sign in. There is also an Crewshal plugin for Claude Code.
  • ChatGPT: add an app with the same address, in developer mode or as a workspace custom app.
  • Codex: install the Crewshal plugin, then codex mcp login agent.

Crewshal opens a consent page. Pick the organization, keep or clear each permission and select Allow.

Permissions

  • Read work: workers, work items and their sessions.
  • Assign work and post messages: needs the member role.
  • Read work context: briefs, checks, evidence, knowledge, specs and the decision log.
  • Search memory.
  • See pending approvals. Deciding them stays in Crewshal.
  • Work on your own plan: take work Crewshal hands to your Claude or ChatGPT, and report results. Needs the member role.
  • Stay connected.

The tool acts as you, within your role. What it posts is marked as coming from the connection. Nothing in the connector approves an action or writes memory.

Revoke

Select Revoke on Connections. An admin can turn connections off for the whole organization there; every connection then stops at once.

From the help article Use Crewshal from Claude, ChatGPT or Codex, checked against the product on .

What you can do

The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.

  • listMcpConnections

    ViewerNo API tokens

    Lists MCP connections.

    Types: EmptyRequest returns ListResponse<McpConnectionDto>

  • revokeMcpConnection

    ViewerNo API tokens

    Revokes the MCP connection.

    Types: RevokeMcpConnectionRequest returns OkResponse

  • getSubscriptionAccess

    Viewer

    Gets subscription access.

    Types: EmptyRequest returns SubscriptionAccessDto

  • updateSubscriptionAccess

    AdminNo API tokens

    Updates subscription access.

    Types: UpdateSubscriptionAccessRequest returns SubscriptionAccessDto

  • listMembers

    Viewer

    Lists members.

    Types: EmptyRequest returns ListMembersResponse

Screens

What it records

The feature writes these events to the audit log, the permanent record of what happened.

  • Connector run reported
  • Connector run started
  • MCP connection revoked
  • Policy changed
  • Vendor trigger fired
  • Vendor trigger removed
  • Vendor trigger saved

Generated from code at commit a7a1a63 ·

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.

Try it on a past pull requestSee how Crewshal works