Connect to Zebra

Connect an app

Connections are initiated from the app to which you're connecting, and every app does it a little differently. You'll set space access and read or write permissions after it connects.

{
  "mcpServers": {
    "zebra": {
      "url": "https://app.zeblink.io/api/mcp"
    }
  }
}

What happens when you connect

The client opens your browser to Zebra's sign-in, then a consent screen that names the app requesting access. You choose whether it may act in all of your Spaces or a selection, and whether it gets full access or may only read. Both choices can be changed at any time from your account's Integrations page — the app does not need to reconnect. A connection acts as you: it can never do more in a Space than your own role allows, and it never sees Spaces outside its grant.

What a connected tool can do

The connection exposes the same actions Zebra's built-in assistant uses: create, edit and delete links, as well as organize manual and smart collections, check path availability, and read analytics — totals, top links, breakdowns, and complex filtered queries. Before anything is deleted, Zebra itself asks the connected app to confirm — nothing is removed on the first request — and everything a connection does is recorded in the Space's activity history.

Managing connections

Connections are listed under Account → Integrations, in a Connected apps table that shows each app's Spaces and access level. Edit either in place, or disconnect an app to remove its access.

Plan and limits

Connecting apps requires a paid plan. Calls count against each Space's API rate limit, shared with API-key traffic. The AI model does its thinking on the client's side, so a connection carries no usage cost in Zebra beyond the requests themselves.