Skip to content

• Ecosystem

All your tools, linked.

Connect the services your work already lives in. zvena brings their records next to your docs and tasks, links what belongs together, and lets you use all of it from your AI assistant, the terminal or your own code.

Create your free workspaceIncluded in zvena Plus and Pro.
See the services

• Services

Any service, by its name.

Type a name in Settings → Ecosystem. These connect ready-made, with the steps to follow; for anything else, zvena works out how to reach it.

Not on the list?

  • Its MCP server

    zvena looks the name up in the official MCP Registry. A service whose MCP server lets apps sign in, as Linear’s, Notion’s and Jira’s do, connects with one click.

  • Its API description

    An OpenAPI or Postman file: zvena reads the lists and actions in it. Try a new connection first: zvena reads each list once and shows what it found, before anything runs.

  • Its webhooks

    Any program that can send a webhook. zvena keeps what it sends and suggests which field is the title, the link and the status.

  • A key, with the steps

    Where a service asks for a key, zvena opens the exact page that makes one, shows which permissions to tick, and says which account it connected as.

• Linked

What belongs together, linked.

A pull request next to its task, an invoice next to its customer, a ticket next to the bug it reports.

  • By what they share

    Records that share an order or invoice number, a customer’s email or the words of a title are found and compared, across every service you connected.

  • Linked, or suggested

    When zvena is sure two records are about the same thing, it links them. When it is less sure, it suggests the link for a person to accept or dismiss.

  • People stay out of it

    Fields about people, such as owners, assignees, emails and phone numbers, are never sent to make that decision, and email addresses and phone numbers in other fields are masked.

  • The owner decides

    The workspace owner can turn smart suggestions off. Then records that share a reference are still suggested, and nothing is linked by itself.

  • Rules across services

    A new deal, a failed deploy, a paid invoice: rules and flows react to what changes in one service and act in another, from creating a task to posting a message.

• Anywhere

Use it from anywhere.

Your workspace is one way in, not the only one.

  • Your AI assistant or code editor

    Add zvena as an MCP server: sign in, pick the workspace, and choose whether it may only read or also make changes. The set-up steps for each app are in Settings → Ecosystem.

  • The terminal

    The zvena command line searches everything you connected, shows what is linked with a record, connects services and runs any of zvena’s tools.

  • Your own code

    A REST API with webhooks and an event feed, described in OpenAPI, and OAuth for the apps you build on it.

The MCP address

https://zvena.app/api/v1/eco/mcp

The command line

curl -fsSLO https://zvena.app/cli/zvena.mjs && node zvena.mjs login

• zvena Link

Services on your own computer or network, without opening a port.

  • It connects out

    zvena Link runs on your computer or server and connects out to zvena. Nothing on your network is opened to the internet.

  • Only what you allow

    It reaches only the addresses you list when you start it, such as an internal tool on localhost.

  • Databases too

    PostgreSQL and MySQL databases on your network can be reached through Link.

  • In the desktop app

    zvena for desktop runs Link itself, with no terminal, and asks you to confirm the addresses it may reach.

  • One token, one machine

    A Link token works on one machine at a time, and a new token stops the old one at once.

• Bridges

Work with another company.

Two workspaces, with the consent of both owners.

  • You choose what crosses

    Each owner picks the projects the other side sees. Their tasks arrive with title, status, priority and due date and stay up to date; assignees and descriptions never cross.

  • Requests across

    An owner can let the other side send requests into the shared projects, and someone there accepts or declines each one.

  • Comments, if you want them

    Comments on the shared tasks can cross too, with their writers’ names.

  • Close it at any time

    Either owner closes the bridge, and what was shown goes on both sides.

Limits, and what to know before you choose.

What it includes, how your data is kept, and what it doesn’t do.

PricingEcosystem API referenceApps for zvena

Plans

  • Included in zvena Plus and Pro; the free plan doesn’t include it.
  • Plus: up to 20 connected services and 3 zvena Links.
  • Pro: up to 60 services and 30 Links, at twice Plus’s request rate.
  • No charge per task or per call. The limits are the plan’s: connected services, Links, requests a second and runs a minute, and the records synced from services (100,000 on Plus, 200,000 on Pro).
  • When a plan ends nothing is deleted: the API and the event feed pause until it runs again.

Your data

  • What a connection brings in is visible to the person who connected it, unless they choose who else sees it.
  • Keys and tokens are kept sealed and are never shown again.
  • An app or assistant you connect does only what its access allows, and you can turn it off at any time in Settings.
  • zvena’s code is open: read it.

What it doesn’t do

  • It doesn’t drive websites that have no API: it connects through a service’s API, its MCP server, its webhooks or zvena Link.
  • A connection zvena worked out for an unlisted service may need fixing when that service changes; zvena tells whoever connected it when it starts failing, and it reconnects in place.
  • Google Calendar and Drive, Microsoft 365, Dropbox, Salesforce and Zoom connect only through a sign-in app: they aren’t offered here yet, unless your workspace’s owner adds its own sign-in app for them in Settings → Ecosystem → Services.

• Your move

Connect the tools you already use.

Create a workspace, choose Plus or Pro, and type a service’s name.