Skip to main content

Overview

The MCP Gateway sits between AI clients and the tools they call. It centralizes connections, credentials, scopes, policies, approvals, and audit records.
Availability may depend on your plan and deployment. Confirm current availability with your Scrums.com contact before designing a production dependency.

Core objects

Governance model

  • Give each person and agent its own identity.
  • Store credentials in a broker instead of client configuration files.
  • Apply policy at organization, team, and individual scopes.
  • Require a separate approver for sensitive actions.
  • Record tool, principal, policy, latency, and outcome for every call.
  • Revoke an agent without revoking the person who configured it.

Connect a client

  1. Add and verify an integration.
  2. Place its connection in the appropriate scope.
  3. Assign tool-level policies.
  4. Create a toolkit for the intended workflow.
  5. Connect the client to the scoped endpoint.
  6. Review audit and approval records.
Last modified on September 15, 2026