mocop
Browse · Docs · Guide · Analyze

XCut AI MCP server

API by XCut AI · rest

XCut AI exposes its agent-facing API as a remote MCP server (Streamable HTTP, JSON-RPC 2.0, stateless). Hook templates, playbooks and quick tools work without an account; tools that read or change the user's XCut AI canvases, brand memory, imports or credits require an OAuth 2.1 access token carrying the scopes below, or a personal API key from XCut AI Settings → Connected apps. Tool and prompt names, schemas and per-tool scopes come from the server itself (tools/list); this document declares the security model and the error model. Developer docs: https://xcut.ai/developers. Agent index: https://xcut.ai/llms.txt.

Endpoint: https://mcp.xcut.ai/

Verification: observed. Source: crawl.

Capabilities (5)

  • RFC 8414 authorization-server metadata (PKCE S256 dynamic client…
  • RFC 9728 protected-resource metadata (scopes_supported authorization_servers)
  • MCP endpoint (Claude build: same server without AI image generation)
  • Liveness check
  • MCP endpoint (full build with AI image generation)
About · Contact · Privacy