Security Overview

How the Stallion MCP server keeps your data safe — OAuth 2.1, read-only access, and scoping to exactly what your account can see.

Security

Read-only by design:

The server observes; it never mutates. There is no tool that changes a release, bundle, rollout, or setting.

OAuth 2.1

The hosted endpoint is secured with OAuth 2.1. In practice this means:

  • No tokens to paste. Your client opens a browser and you sign in through the Stallion console — or it's silent if you're already logged in.
  • Your login methods. Sign in with email OTP, SSO, or passkey — whatever your organization uses.

Scoped to your account

Authentication inherits exactly your user's access scope. The assistant can only see the organizations, projects, and releases that you can see in the console. There is no elevated or shared access.

No secrets exposed

Configuration responses are deliberately filtered. For example, get_project_detail returns platform and patch settings — but never secrets like CI tokens, app tokens, or signing material.

Questions?:

For enterprise security reviews or questions about the MCP server, reach out via the contact page.