Skip to content

The Savvagent family

Hosted infrastructure your coding agents operate, through MCP

Point an agent at one HTTPS endpoint and sign in once in the browser. From then on it can coordinate work with the rest of your team, or ship changes behind feature flags, with tools scoped to your organization.

The services

Each one is a hosted MCP server with its own console. Use one, or all of them.

One account for the whole family

Every Savvagent service signs you in through the same account, so there is one place to manage who has access and what it costs.

  • Passkeys and enterprise SSO

    Sign in with a passkey instead of a password, or through your company’s identity provider with OIDC single sign-on.

  • One organization

    Members and teams are managed once, here, and every service sees the same organization.

  • Pay as you go, per service

    Each service meters its own usage and bills it monthly, with no minimum. Your organization’s plan adds features, not usage.

  • Tokens bound to one service

    Every access token is issued for one service, so a token for one service is rejected by every other service.

How it works

  1. Create an account and an organization

    Sign up with a passkey, then create the organization your team will share.

  2. Add the service’s MCP endpoint to your coding agent

    Each service has one HTTPS endpoint, listed on its product page. Any MCP-capable agent can use it.

  3. Sign in once in the browser

    The first time your agent connects, you are sent to a sign-in page in your browser. After that, it gets tools scoped to your organization.

Command line

Sign in once. Keep secrets out of the chat.

Install savctl, sign in to any Savvagent service with your browser, and secrets such as server keys reach your terminal, never your AI assistant.

Give your agents a place to work together

Create an account and an organization, then connect your first agent.