Connect Z4PS to your AI client
Z4PS provides a remote MCP server with OAuth. A connection is scoped to one workspace and the permissions you approve.
Client verification is still pending. ChatGPT, Claude and Codex connections have not been tested in their actual clients. Their available connection settings and plan requirements vary. This guide describes the server setup; it does not guarantee compatibility with a particular client.
Connection details
- Server URL
https://z4ps.uk/mcp.php- Transport
- Streamable HTTP
- Authentication
- OAuth authorization code with PKCE; sign in on Z4PS
- Access
- One chosen workspace; read-only or read/write
- Create a free Z4PS account and verify your email, or sign in to your existing verified account.
- In a client that supports remote MCP with OAuth, add the server URL above. Follow the client's sign-in action.
- On the Z4PS authorization screen, check the client name, choose your workspace and approve the required access.
- Ask the client to list your links first. If that works, approve write access when you need link creation.
A connection lasts up to 30 days. Access tokens refresh automatically when your client supports it; reconnect after the connection expires. Deletion needs a separate permission and exact confirmation.
If your client does not support this OAuth flow, do not paste your Z4PS password, session cookie or token into a chat. Use the dashboard instead. You can revoke connections on the AI connections page.
Try a useful first request
"List my recent Z4PS links. Then create a short link to https://example.com/launch with newsletter UTM tags and a plain QR code. Ask me before making changes."
Read-only connections can list and inspect data. Creating links requires write permission; the free plan includes core creation, UTM, expiry, plain QR and analytics tools within its existing limits.
Tools and plans
| Plan | Tools |
|---|---|
| Spark / free | get_profile, get_account, list_links, get_link, create_link, build_utm_url, get_link_qr (plain PNG), get_analytics, compare_links, list_bio_pages, get_bio_page. update_link can set, change or remove expiry for free. delete_link requires explicit slug confirmation. |
| Bolt and above | Also destination and password edits through update_link, and bulk_create_links. Styled QR codes are available in the website; the MCP QR tool returns plain PNG. |
| Surge and above | Also list_campaigns, create_campaign, update_campaign, delete_campaign, list_link_rules, create_link_rule, update_link_rule, delete_link_rule, including weighted A/B and country/device targeting. |
Write tools also require workspace write permissions. Analytics tools return daily totals within inclusive UTC dates, with human and bot counts separate; comparisons rank selected links. They do not expose country, device or referrer breakdowns. Role restrictions, monthly allowances, slug limits and safety checks still apply. The REST API remains a separate Bolt-and-above interface.
Check the output before sharing
Confirm the destination, campaign labels, expiry and QR code before publishing a link. Click reports show available activity; they cannot prove sales or identify individual people. Destination content is not fetched for your AI client by these tools.
Common connection problems
- Sign-in does not return to your client: restart the client connection flow. Authorization requests expire and callback URLs must match the client registration.
- A tool is refused: check connection permissions, workspace role and the feature's plan requirement.
- Your token no longer works: the connection may have expired or been revoked. Reconnect through OAuth.
- The server is unavailable: public AI connections may still be disabled during rollout. Your dashboard and normal short links remain available.
Know what you are sharing
Your selected AI client receives results from the tools it calls, which may include destinations, campaign labels and analytics from your workspace. Its own privacy policy governs how it handles those results. Z4PS keeps a short operational audit without prompts, tool arguments or response content. Revoking access stops future requests; it cannot recall results already received.