> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/control-center/govern/connectors.md).

# Connectors

Review which outside systems and platform skills agents can use, and their standing.

Connectors is the account-wide register of what an agent is allowed to reach outside itself — third-party integrations, MCP servers, and the platform's own built-in skills. Open **Governance → Controls & Policies → Connectors**.

Every agent inherits this as its outer limit: an agent can't use a connector this account hasn't made available, regardless of what its own configuration requests.

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-ef891f082127ac4021969e0da829bbd388a13f89%2Fqore_control-center_control-centre-govern-connectors-integrations_rounded_shadow.png?alt=media" alt="The Connectors page, Integrations tab, listing third-party connectors with their description, Standing, and Tags"><figcaption><p>Connectors, on the Integrations tab.</p></figcaption></figure>

Search narrows all three tabs by name.

## Integrations

Third-party systems available to the account, such as core banking platforms, CRMs, and document-processing services. Each row shows:

| Field           | What it shows                                                                    |
| --------------- | -------------------------------------------------------------------------------- |
| **Connector**   | The integration's name and icon.                                                 |
| **Description** | What it connects to and what it's for.                                           |
| **Standing**    | Whether agents may use it — currently **Allowed**.                               |
| **Tags**        | Its category, such as **Banking**, **Compliance**, **CRM**, or **Productivity**. |

This is the same catalog behind [Integrations Hub](/integrations/integrations-hub.md) — Connectors is where you review standing across the whole account; Integrations Hub is where you connect one for a project.

## MCP servers

Model Context Protocol servers available to the account, alongside the third-party integrations and platform skills. Configure and review them the same way — by Standing and the projects and agents using them.

## Platform skills

Qore's own built-in skills — reasoning, web search and crawl, code execution, document and knowledge operations, and UI-rendering skills like Display Code Block and Display Document. Each row shows:

| Field         | What it shows                                      |
| ------------- | -------------------------------------------------- |
| **Connector** | The skill's name, tagged **Platform skill**.       |
| **Standing**  | Whether agents may use it — currently **Allowed**. |
| **Project**   | The project it was used from.                      |
| **Used by**   | The agent that used it.                            |

<figure><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-3c2f82cdb6f32c3270b79a53ccec92907e3427bf%2Fqore_control-center_control-centre-govern-connectors-platform-skills_rounded_shadow.png?alt=media" alt="The Connectors page, Platform skills tab, listing built-in skills like AI Reasoning, Web Search, and Run Python with their Standing, Project, and Used by columns"><figcaption><p>Connectors, on the Platform skills tab.</p></figcaption></figure>

{% hint style="info" %}
Platform skills and MCP servers list **Project** and **Used by** per row because they're attributed to the agent that invoked them. Integrations list **Tags** instead, since a third-party connector is a standing account capability rather than a per-use record.
{% endhint %}

## Related

<table data-view="cards"><thead><tr><th>Title</th><th>Description</th><th data-card-target data-type="content-ref">Link</th></tr></thead><tbody><tr><td><strong>Integrations Hub</strong></td><td>Connect a third-party integration for a project.</td><td><a href="/integrations/integrations-hub.md">Integrations Hub</a></td></tr><tr><td><strong>Agent Controls</strong></td><td>Stop individual agents or all agents during an emergency.</td><td><a href="/control-center/govern/agent-controls.md">Agent Controls</a></td></tr><tr><td><strong>Audit Trails</strong></td><td>Review configuration and access changes over time.</td><td><a href="/control-center/observe/audit-trails.md">Audit Trails</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.uptiq.ai/control-center/govern/connectors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.