AI & agents
Your collection, one conversation away.
Connect an AI assistant to Holo Folder through MCP, the Model Context Protocol. Your assistant can search cards, read your binders and wanted lists, and check available prices using the same data as the app.
Sign in with your Holo Folder account. Choose what the assistant can access. No API key, local server or client secret to manage.
Choose your assistant
Claude
Connect Claude Code over HTTP, or add Holo Folder as a custom connector in Claude.
ChatGPT
Add a custom MCP connection where your account and workspace support it.
Cursor
Add the remote server to your MCP configuration and authorise it in Cursor.
Codex
Connect the Codex CLI or configure a remote MCP server in your coding environment.
The connection details
Every compatible client uses this Streamable HTTP endpoint:
https://app.holofolder.com/app/mcpChoose OAuth when prompted. Compatible clients discover registration and authorisation from the server's authentication challenge. Do not paste a REST API key into an MCP connection.
A current Premium subscription or lifetime licence is required. Signup trials do not include developer access. Partners follow the paid collection owner's access and current membership.
Make the first connection
- Add the server in your client using its setup guide above.
- Follow the browser sign-in flow to Holo Folder.
- Check the client name, redirect host and requested access on the consent screen.
- Approve the connection, then return to your assistant.
Start with read permissions. Writes, sharing and partner changes need explicit approval.
Clients running on another machine
If your agent runs on a remote machine, in an SSH session or in a container, a localhost callback points at that environment. Opening it in your browser reaches your own device instead.
On the consent screen, select My client is on another machine before approving. Holo Folder will keep the callback URL on screen. Choose Copy callback URL, send it to the agent you are connecting, and ask it to open that URL on the machine where the MCP client is waiting. If copying is unavailable, select and copy the URL from the text field. Keep the client waiting while you do this; if the request expires, start a new connection.
An already-approved connection with a localhost callback also shows this handoff. If the client is on your device, choose Open on this device to continue locally. Holo Folder cannot automatically forward a localhost callback to a remote machine; that requires forwarding support from the client.
Try a first prompt
List my binders, then show the wanted cards in one I choose.
Don't change anything in my collection.Or ask it to search the catalog for a particular Pokémon or read the available price evidence for a card. Missing prices stay missing; your assistant should not guess them.
Agent setup & API discovery
Building your own agent? Use an OAuth-capable remote MCP client with the server URL above. The server exposes tools from the same operation registry as the REST API. Tool names and required permissions appear on each endpoint page.
For an agent that calls REST directly, use a personal API key and the OpenAPI document. Read API conventions before enabling writes, retries or pagination.
The developer endpoint connects directly to the app host so OAuth discovery headers reach your client. Sign-in and consent still open on the Holo Folder website. If you previously configured https://holofolder.com/app/mcp, replace it with the URL above and connect again.
Manage access
Revoke a connected assistant from Settings → Account → Developer access. A revoked connection must authorise again; reconnecting does not restore access to its old tokens.
MCP follows the same paid-access requirements, data permissions and provider limits as REST. If a connection fails, check that your client supports remote Streamable HTTP and OAuth, that paid access is active, and that your workspace allows custom MCP servers.