Skip to main content
Connectors let the Assistant use tools outside Zudo while it answers: search your issue tracker, read a page in your wiki, look something up in an internal system. Anything that runs an MCP server can be a connector. Ask the way you normally would: “Is the export bug Acme raised fixed yet?” The Assistant reads Acme’s request in Zudo, finds the issue through your tracker’s connector, and answers from both. Each lookup shows in the answer like any other, as “Linear: Search issues”.

​
Adding a connector

Admins add connectors in Settings → Organization → AI, under Connectors. Choose Add connector and give it:
  • a name, such as “Linear”, which is what the Assistant and your team call it
  • the MCP server address, which must start with https://
  • optionally, what it’s for, such as “Engineering issues and what’s shipping”, which helps the Assistant know when to use it
Zudo connects to the server before saving it, and works out how it signs in:
  • No sign-in. The server answers without one, so Zudo lists its tools straight away.
  • Each person signs in. The server asks for an account, as most services do. You sign in next, with your own account, so Zudo can list the tools for you to review. Everyone else connects their own account later.
  • A shared token. Some servers take a token instead. Open The server uses a token, or needs a client ID and paste it. Everyone in your organization then uses that token through the Assistant, so choose one with only the access the whole team should have.
Most services let Zudo register itself when you sign in. A few need an OAuth app made by hand first: create one at the service with the redirect address below, then enter its client ID and secret when you add the connector.
An organization can have up to 10 connectors.

​
Choosing what the Assistant may do

Each of a connector’s tools has one of three settings: When Zudo first lists a connector’s tools, tools the server says only read are Allowed, tools it says delete are Off, and everything else Needs approval. Those are the server’s own descriptions, so read them before allowing a tool, especially one that changes things. A connector stays off until an admin turns on On for your team, which needs at least one tool that isn’t off. The Assistant only ever sees the tool descriptions you reviewed. If the server changes them, nothing changes in Zudo until an admin chooses List tools again: new tools then arrive off, and tools whose description changed are marked so you can look again.

​
Connecting your account

Where a connector signs each person in, choose Connect beside it in Settings → Organization → AI and sign in to that service. The Assistant then uses that service as you, and sees only what you can see there. Until you connect, it tells you to when a question needs that connector. Choose Disconnect to remove your sign-in from Zudo. The service may still list Zudo as connected until you remove it there too.

​
What reaches the connector

When the Assistant uses a connector, the service receives what that call needs: the search terms, the issue number, the values on the review card. It doesn’t receive your chat. What the connector sends back becomes part of the conversation, so it goes to the AI provider answering your question, like everything else the Assistant reads. The Assistant treats it as information to report, never as instructions, but text written by someone outside your organization can still try to steer it. Only add servers you trust, and keep tools that change things on Needs approval.

​
Limits

  • Connectors are tools only. The Assistant doesn’t read an MCP server’s prompts or resources.
  • Each connector offers up to 100 tools. A tool whose description is too large to send stays off.
  • Long results are cut short, and a call that takes longer than 60 seconds is stopped.
  • Connectors are only available in the Assistant, not through Zudo’s API or MCP server.
  • Zudo connects only to public https addresses, never to private or internal networks.

​
When someone leaves

Removing a member from your organization removes their sign-ins to its connectors. Removing a connector removes everyone’s sign-in to it.