| name | titles-setup |
| user-invocable | true |
| description | Use when the user wants to connect their agent to TITLES, set up the TITLES MCP server, authenticate with TITLES, or when TITLES MCP tools are missing or returning authentication errors. Covers adding the server endpoint, the OAuth flow, verifying the connection, and troubleshooting. |
TITLES MCP Setup
Connect this agent to the TITLES MCP server so it can generate images, discover models, manage sessions, and publish results on TITLES.
Before you start: log in to titles.xyz
Have the user log in to titles.xyz in their default browser first (creating the account there if they don't have one). The OAuth approval then takes one click, which keeps it inside every client's authorization window — most connect-flow failures ("failed to connect", timeouts, lost callbacks) are really the browser step outlasting the client's patience while the user logs in or signs up mid-dance.
Server details
- Endpoint:
https://mcp.titles.xyz/mcp
- Transport: Streamable HTTP
- Auth: OAuth 2.1 with PKCE and dynamic client registration (RFC 7591). No pre-registered client ID or API key is needed — MCP clients register themselves automatically and open a browser for the user to approve access with their TITLES account.
- Discovery: standard well-known documents are served at
https://mcp.titles.xyz/.well-known/oauth-authorization-server.
Add the server
Use the client's native MCP configuration. Examples for common agents:
Claude Code
