Audit trail API
Sessions and calls are Registry artifacts of kindmcp_session and mcp_session_message. The same aggregation and list APIs that work for any artifact work here.
- REST: count calls per day
- MCP: read calls from agent
created_at. To break calls down by server_slug, tool_name, or outcome, read the call rows individually. To count sessions by client, group mcp_session by atlan_client.Catalog limits
Client to gateway
Credentials for your servers
A server uses either one shared credential or per-user OAuth, not both.
Certificate and SSH-key credentials are not supported. The gateway injects a
single header per server.
Errors your client may see
When a server needs your sign-in or cannot be reached, the rest of the catalog
still works. In search mode, a search or describe lists the server under
connect with a reason, or marks the result partial. In full mode, the
gateway drops the server’s tools from tools/list and names it in the result’s
_meta.
Gateway to your MCP servers
Governance
MCP Apps
Use MCP Apps to display a declared tool view in Studio or a compatible client. Availability depends on the environment’s Apps configuration.
See MCP App metadata and resources for storage, resource reads and size limits. A declared view is not a guarantee that every third-party App’s required capabilities are supported.
Server connection states
Until a person connects to a per-person server, its tools are hidden from that person’s
tools/list, and the result names the server so the client can prompt them.
Tool catalog API
An application that picks tools for its users, or an inventory or governance report, can search the catalog without an MCP client using the Search the tool catalog endpoint:
Each result is a catalog row with
owner, server_id, and tool_name. Build the full tool name from them as described in Tool names. GET /mcp/v1/tools lists the whole catalog. An agent in full mode can search the same catalog with registry__search_artifacts, kind set to mcp_tool.