> ## Documentation Index
> Fetch the complete documentation index at: https://www.osohq.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connectors

> Review the MCP servers, CLI tools, and integrations your agents actually call.

Oso discovers every connector - an MCP server, a CLI tool, or a built-in shell integration - that agents call in your traffic, and lets you review it before deciding how to treat it in policies.

## Needs review vs. Reviewed

Connectors sit in one of two views:

* **Needs review** - connectors discovered in your traffic since your last review, with at least one tool still awaiting triage.
* **Reviewed** - connectors where every tool has been triaged.

A connector moves from Needs review to Reviewed once you've reviewed all of its tools, not necessarily all at once.

## What you see

| Column | Description |
| - | - |
| **Connector** | The connector's name and icon |
| **Type** | MCP, CLI, or Built-in |
| **Last seen** | When the connector was last used |
| **Recent uses** | Session count over the recent lookback window |
| **Agents** | Which agents have used it |
| **Users** | Which users have used it |

## Reviewing a connector

Click into a connector to open its detail panel:

* **Configuration** - connection details for MCP/CLI connectors (transport, URL, command, and similar)
* **Provider** - assign or change which upstream system the connector belongs to (for example, classifying an MCP server as GitHub), so it can be matched by a **Provider** condition in [Policies](https://www.osohq.com/docs/oso-for-agents/policies.md)
* **Tools** - the tools discovered under this connector
* **Sessions** - recent activity through this connector, with a link to view all of it
* **Policies** - once reviewed, which policies already cover this connector, with a shortcut to create one scoped to it

To finish reviewing a pending connector, mark it as reviewed. If policy creation is enabled for your account, you can optionally add a policy inline first, starting from a quick-start template (Escalate writes, Read-only, Block everything, or a custom rule) before finishing the review.

A progress indicator above the queue shows how many connectors you've reviewed and how many remain.

## Adding connectors proactively

Rather than waiting for traffic to surface a connector, use **Add connectors** to search Oso's catalog and add a cataloged connector straight to your review queue in advance. This only works for connectors Oso already recognizes; anything outside the catalog still needs to show up in traffic before you can review it.

## Using connectors in policies

Once a connector has a classified provider, or once you know its connector name, both become available as conditions when [writing a policy](https://www.osohq.com/docs/oso-for-agents/policies.md):

* **Operation → Connectors** - matches every call made through that specific CLI or MCP integration
* **Resource → Provider** - matches by the upstream system the connector belongs to

You can also jump straight into the policy builder, pre-scoped to a connector, from its detail panel.

## Where to find it

Connectors live under **Discover → Connectors** in the Oso dashboard.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.