Showcase MCP
BetaConnect Showcase to an MCP-compatible AI assistant. After you sign in and approve scopes, the assistant can work with the same protected Showcase content and preferences exposed by the tools below.
https://showcase-app.co/mcpWhat you can do
Find and understand
Search your Library, nested and collaborative collections, artefacts, Quick Note, collection activity, Explore history, scheduled runs, and Ask AI threads.
Create and organize
Create, update, move, copy, reference, archive, share, arrange, shuffle, upload and download files, and format content and canvas size.
Collaborate and connect
Use collaborators, reminders, Ask AI, account preferences, transcripts, and integration connect, sync, hide, and disconnect flows.
Protected actions
Deletion uses separate confirmation tokens. File transfers use short-lived, permission-checked links. Provider OAuth, snapshot downloads, and account deletion remain in Showcase so native consent and warnings stay authoritative.
Connect
In ChatGPT or another client that supports remote MCP, add the server URL above and complete the Showcase sign-in and consent screen.
Codex CLI
codex mcp add showcase --url https://showcase-app.co/mcp
codex mcp login showcaseOther MCP clients use the same HTTPS endpoint and OAuth flow; exact setup commands vary by client.
Safety and limits
- • Every tool checks the signed-in user, OAuth scopes, and Showcase permissions on the server.
- • Read and write calls have per-connection and per-user rate limits; invitations and MCP upload bytes have additional daily limits.
- • Large uploads use exact-size presigned policies and are verified again before an artefact is created.
- • Downloads use five-minute signed resource links rather than permanent credentials.
- • Hard ceilings prevent unbounded collections and artefacts, including paid or unlimited accounts.
Important
An AI assistant can only use tools its client supports and only the permissions you approve. Showcase still enforces authorization and limits for every call. Tool descriptions and client-side confirmation screens are helpful user-interface signals, not substitutes for server-side protection.