1
Add the connector
In your MCP-compatible AI assistant, add a remote server using the URL above. Choose OAuth authentication if prompted.
Your Zipy workspace.
One conversation away.
Bring links, bio pages, files, and QR codes into your AI workflow. Connect your account once and work with the tools already included in your plan.
REMOTE MCP SERVER · STREAMABLE HTTP
https://mcp.zipy.cc/mcp2
Connect your account
Sign in to Zipy and review the requested permissions. Your API access and plan capabilities apply automatically.
3
Start with an idea
Ask your assistant to create a campaign link, build a bio page, generate a QR code, or check your link analytics.
The tools behind your next idea.
Short linksBio pages & blocksQR codesFile uploadsStatic websitesSplash pagesvCards & eventsProjects & pixelsDomainsAnalytics
Available actions depend on your account, the enabled Zipy features, and your current plan.
Built around your account.
Which AI assistants can connect?
Use an assistant that supports remote MCP over Streamable HTTP and OAuth, including compatible connector offerings from ChatGPT, Claude, Perplexity, and other clients. Connector availability, write support, and setup screens depend on the assistant’s plan and policies. This endpoint is not an automatic marketplace listing.
Who can use the connector?
MCP uses the same entitlement as Zipy’s API. The administrator must enable the API globally and include API access in your plan. Disabling access also blocks existing MCP connections.
How do permissions and disconnection work?
Each client connects to your own account with an expiring OAuth token. Read-only connections cannot change assets. Manage access permits creation, editing, and deletion within your plan. You can revoke any connection at AI connections. Your Zipy API key is not shared with the AI client.
How do files reach Zipy?
Clients can send actual file bytes as base64, up to 10 MB per request, subject to Zipy’s native file type and size rules. Uploading depends on your client’s file capabilities. Larger files can be uploaded directly through your Zipy dashboard. Static sites accept HTML or validated ZIP archives.
Technical connection details
Transport: stateless Streamable HTTP with JSON responses. OAuth: authorization code with S256 PKCE, dynamic client registration, rotating refresh tokens, and token revocation. Scopes: zipy:read and zipy:manage. Discovery is available at the standard OAuth well-known endpoints. The server does not expose administrator controls.