> 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/cookbooks/platform-admin/agents-and-evidence/review-what-agents-can-reach.md).

# Review connector access

There is no API for this today. What to use instead, and what to ask for.

This recipe has no request to show. **No endpoint across any of the seven QA services returns the Connectors register** — the account-wide list of integrations, MCP servers and platform skills agents inherit as their outer limit, which Control Center's Govern → Connectors page displays.

## At a glance

| Item               | Value                                        |
| ------------------ | -------------------------------------------- |
| ⚙️ Feature         | Connector access register                    |
| 🌍 Environment     | QA                                           |
| ⌘ API endpoint     | Not available                                |
| ✅ Supported method | Control Center → **Govern** → **Connectors** |

{% columns %}
{% column %}

#### What you can do

Review the account-wide connector register in Control Center.
{% endcolumn %}

{% column %}

#### What isn't available

No public API returns the connector register.
{% endcolumn %}
{% endcolumns %}

{% hint style="danger" %}
**Genuine gap, not an oversight in this cookbook.** Every other admin task in this set has a working recipe. This one doesn't, because the operation doesn't exist in the public API surface as of this documentation's verification date.
{% endhint %}

## What to use instead

| Need                                | What to use                                                                                                                                                                                                                                               |
| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Review the connector register       | Use [Review connector access](https://docs.uptiq.ai/platform-guides/admin/agents-and-evidence/review-connector-access) in Control Center.                                                                                                                 |
| Call a resource-specific MCP server | Use its `mcp` endpoint, such as `/audit-logs/mcp`, `/teams/mcp`, or `/users/mcp`. Send JSON-RPC with `accept: application/json, text/event-stream`. See [Review the audit trail](/cookbooks/platform-admin/agents-and-evidence/show-who-changed-what.md). |
| Inspect standing connector access   | No API exists. MCP tools report activity, not the full list of integrations, MCP servers, and skills an agent can access.                                                                                                                                 |

## If you need this via API

Raise it with your UPTIQ contact. Include what you'd query, and how often. A machine-readable connector register isn't a documented roadmap item.

## Related

* [Review connector access](https://docs.uptiq.ai/platform-guides/admin/agents-and-evidence/review-connector-access) — as a screen
* [Assign agents and apps to a team](/cookbooks/platform-admin/give-people-access/give-a-team-access.md)
* [Stop an agent](/cookbooks/platform-admin/agents-and-evidence/stop-an-agent.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.uptiq.ai/cookbooks/platform-admin/agents-and-evidence/review-what-agents-can-reach.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.