Connect any MCP client

SageOx speaks the standard MCP protocol with OAuth 2.1 + Dynamic Client Registration (RFC 7591). If your tool supports MCP, this is everything it needs.

Server URL

https://sageox.ai/mcp

mcpServers config

For tools that use a JSON config file:

{
  "mcpServers": {
    "sageox": {
      "url": "https://sageox.ai/mcp"
    }
  }
}

How auth works

On the first call to the SageOx MCP server, your tool will:

Get a 401 whose WWW-Authenticate header points to the resource metadata at /.well-known/oauth-protected-resource/mcp
Read the authorization server metadata at /.well-known/oauth-authorization-server
Register itself via DCR at /api/auth/oauth2/register (PKCE S256 required)
Open a browser tab to the OAuth consent screen at /api/auth/oauth2/authorize
Exchange the auth code for an access token at /api/auth/oauth2/token
Use the bearer token for all subsequent MCP calls

This is the standard MCP authorization flow, so any MCP-compliant client can connect without SageOx-specific setup.

Tools available

These are the tools most conversations start with:

Tool	What it does
`GetStarted`	Explains SageOx and walks a new user through setup
`Prime`	Primes your AI coworker with your team's conventions, recent decisions, who's on the team, and current focus
`Search`	Searches your team's Discussions, docs, Sessions, and Murmurs (ChatGPT uses lowercase `search` and `fetch` instead)
`ListTeams`	Lists the teams you belong to
`ListBubbles` / `ReadBubbleFile`	Lists the Knowledge Bubbles you can see, and reads their curated files
`ListRecordings` / `ConversationTranscript`	Lists a team's recent Discussions, and returns one Discussion's full transcript
`SaveSessionSummary`	Saves a distillation of the conversation, once you've confirmed it, as a Session in Team Context
`PublishMurmur` / `ListMurmurs`	Posts and reads short work-in-progress notes your teammates see
`Help`	Answers how-do-I questions and explains how to recover from a tool error

Your client's tools/list is the source of truth: it carries the full set, with each tool's schema and description, and the set can differ by client. Scopes are surfaced on the OAuth consent screen.

Managing connections

/settings/security lists all active grants. Revoke per-client or all at once, revocation invalidates the access token, so the next MCP call returns 401 and the client cleans up its local state.

What's next

Getting the most out of SageOx: how to prompt your AI coworker well and what the interactive cards do
MCP overview: what MCP gives your tool and how to manage connections