
Covers Permissions MCP Engineering
Description
Use an authenticated Centaur MCP deployment to discover and call team-approved tools. Use when a task requires Centaur, its tool catalog, or the user's Centaur identity and permissions.
SKILL.md
Centaur
Use Centaur's MCP tools for actions and context exposed by the user's deployment.
Workflow
- When identity or authorization matters, call
centaur_whoamibefore other Centaur tools. - Choose the narrowest Centaur tool that satisfies the request.
- Each tool package accepts a
methodand anargumentsobject. If its methods or parameters are unclear, call that tool withmethod: "help"first. - Treat the MCP tool description and help result as the current contract. Do not guess method names or parameters.
- Summarize consequential writes and return relevant identifiers or links.
Centaur authorizes calls using the signed-in principal's live roles and grants. Never request, paste, print, or store Centaur OAuth tokens.
Connection recovery
If no Centaur tools are available, explain that the client still needs the deployment-specific MCP endpoint.
- Codex: register it with
codex mcp add centaur --url <CENTAUR_MCP_URL>, then runcodex mcp login centaur. The--urlflag is required for Streamable HTTP and OAuth. - Claude Code: configure the plugin's
mcp_url, open/mcp, and authenticate thecentaurserver. - Other MCP clients: configure a remote HTTP server named
centaurwith the deployment's/mcpURL and complete its OAuth flow.
Do not substitute a guessed hostname. Ask for the deployment URL when it is not already configured or supplied.