August 2026 release is live Read More
Breadcrumbs

Connector

What it is

A Connector links the Mavvrik Agent to a tool your team already uses — Jira, GitHub, Sentry, or any other MCP-compatible server. Once connected, the Agent can look things up or take actions in that tool directly from a Chat conversation.

Why this matters: a Connector is like giving the Agent its own login to a tool you already use, instead of you having to check that tool yourself and bring the answer back into the conversation.

This shows up differently depending on your role:

  • Admins set up and authorize Connectors for the team.

  • FinOps managers and engineers benefit by asking cross-tool questions directly in Chat, without switching tabs.

What you can do with it

  • Look up a ticket. Ask about a Jira issue's status without switching tabs.

  • Check a pull request. Ask whether a GitHub PR would affect your cloud bill before it merges.

  • Correlate signals across tools. Ask whether a recent error spike (Sentry) lines up with a cost spike, and get an answer that draws on both.

How to add a Connector

  1. Go to Connector in the Agent's admin area.

  2. Click the Connector button to open the "Add Connector" dialog.

  3. Fill in:

    • Name and Description

    • URL — the address of the MCP server you're connecting to

    • Transport — Streamable HTTP or SSE

    • Authentication — None, Basic, Bearer, or OAuth, depending on the tool

  4. Click Create.

If the tool uses OAuth (e.g. Jira, GitHub)

After clicking Create, you'll be taken to that tool's own authorization screen to sign in and approve access.

Before you start an OAuth connection: your Atlassian (or other OAuth provider) org admin may need to allowlist Mavvrik's redirect URL first. If you see a message saying your organization admin must authorize the redirect URL, this step hasn't been done yet for your org — check with your admin before trying to connect again. Once it's allowlisted, any user in your org can complete the authorization.

Ownership note: a Connector's authorization is tied to whoever completed the OAuth flow. If that person leaves or their access to the underlying tool is revoked, the Connector's status will show Disconnected — reauthorize it with a current account rather than leaving it in that state.

How it works day-to-day

  • A Connector's status shows as Connect (not yet authorized), Connected (ready to use), or Disconnected.

  • Once a Connector shows Connected, mention the tool by name in a Chat question (for example, "using GitHub, check…") and the Agent will use it directly — no extra setup per question.

  • You can see how many tools a Connector exposes from its row in the Connectors list.

Good to know

  • Connectors are the only way to give the Agent reach into your own systems — Skills shape how it reasons, Connectors extend what it can actually do.

  • If a question needs a tool that isn't connected yet, the Agent will tell you rather than guessing — you'll get an honest "not connected" instead of a fabricated answer.

FAQs

What happens if I ask about a tool that isn't connected yet?
The Agent tells you it isn't connected rather than guessing or fabricating an answer.

Do Skills and Connectors do the same thing?
No — Skills shape how the Agent reasons, Connectors extend what it can actually do by giving it reach into your other systems.