Remote MCP tool servers as connectors

The idea

An org connects outside MCP tool servers as governed connectors, granted per worker or role. Risk comes from the tools' annotations, and the database serializes each OAuth refresh.

The problem
Outside tools would bypass the gateway's policy and audit.
Why it matters
Any MCP server becomes a governed tool, and short-lived connections are reused.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • One governed tool gateway

    Every action goes through one gateway. It checks authorization, policy, risk, budget and approval, writes the action ledger first, and reads back each external write. A model answer can only add a requirement.

  • Crewshal inside Claude and ChatGPT

    Crewshal is an OAuth remote MCP server packaged as connectors and plugins, and a worker can fire the requester's own Claude routine or ChatGPT agent trigger after approval.

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.