Skip to main content
Visibility MCP lets a compatible AI client answer questions using the Oximy data you are already allowed to see. It can read information about people, departments, tools, observed usage, supported spend, and tool review status. It cannot change Oximy settings or approve actions.

Connect your client

1

Open your client's MCP settings

Add a remote MCP server using the setup flow provided by your AI client.
2

Enter the server address

Use https://mcp.oximy.com/mcp.
3

Sign in to Oximy

Complete the Oximy sign-in flow. If you belong to more than one organization, choose the organization whose Visibility data you want to query.
4

Test the connection

Ask the client to describe the Visibility information it can query, then try a narrow question such as which tools have activity in a department.

Ask questions with a clear scope

State the population and time period you want to understand. For example:
  • Which tools did the Engineering department use in the last 30 days?
  • Which people have activity for an approved tool in this period?
  • How is observed usage distributed across use cases?
  • What billed spend evidence is available for each tool?
For a long list, ask the client to retrieve every page before summarizing. When comparing two results, use the same organization, population, access scope, and time window.

Understand the access boundary

The connection uses your current Oximy workspace membership and Visibility access policy. It does not grant broader organization, financial, or content-level access. A missing record or field can mean that it is outside your access scope, the connected source does not provide it, or there is no matching data. Do not treat an omitted value as zero.
Visibility MCP is read-only. To approve a tool, change access, or update a policy, use the corresponding workflow in Oximy.

Reconnect to another organization

If you connected the wrong organization or the connection has expired, remove or reconnect the server from your AI client’s MCP settings and complete the Oximy sign-in flow again.