Skip to main content
machina connect is the one-command bridge that lets an external agent (e.g. sportsclaw) talk to a project’s MCP endpoint — it resolves the endpoint and pairs it with an auth token, ready to register, without a hand-pasted URL or key.

Usage

Examples

What you get

  • The MCP URL, transport (sse), and auth header (X-Api-Token) — the same derivation as machina mcp url.
  • A token paired to that endpoint. By default the ambient session/API-key credential; with --mint, a durable dedicated sportsclaw-<project> project API key (reused if it already exists, minted if not — so the connection survives your session expiring).
The token is masked unless you pass --reveal. Treat a revealed token as a live credential — it grants access to the project’s MCP surface. --mint keys are scoped per project and named sportsclaw-<project>; manage them with machina credentials.
  • mcp url — the raw endpoint resolver (no token pairing).
  • credentials — list/revoke the project API keys (--mint reuses these).