Skip to main content
Claude Code calls MCP tools as the person who connected it. Linear, Slack or PostHog can’t tell that call apart from one the person made by hand, and Claude Code keeps no shared record. To audit it, the calls have to pass through something that writes them down. With Oriant, Claude Code connects to your MCP server through an Oriant connection. Every call is recorded before it is sent on.

Set it up

1

Add the MCP server in Oriant

Open MCP Connections and add the server, for example Linear. See MCP Connections.
2

Point Claude Code at Oriant

Then run /mcp in Claude Code and sign in. Remove any old entry that points straight at the server.
3

Open the call log

Each call shows up on the connection’s page as it happens.

What a record holds

Each row is one tool call: when it happened, who it acted for, the tool, the AI client, the status, and the policy that decided it. The example below leaves out the AI client column, since every row is Claude Code. Open a row to see the arguments Claude Code sent. The rows above are an example. The tool’s result is never stored, so the log shows what Claude Code asked for, not what it got back.

Status

  • Succeeded: the tool ran.
  • Tool error: the tool ran and answered with an error, such as “issue not found”.
  • Failed: the call didn’t complete.
  • Refused: a policy or argument rule stopped it. It was never sent.
  • Unknown: the call was sent, but the result never came back. It may have run.

Find calls that skip Oriant

Someone can still add the server straight to their own Claude Code config. Those calls don’t reach Oriant. The endpoint agent reports the MCP servers in each machine’s AI client configs, and the Coverage tab lists the ones that don’t go through Oriant.

Ask Claude about it

Oriant MCP lets an Owner or Admin ask their own Claude Code questions like “which tools did Claude Code refuse this week?” without opening the dashboard.
Last modified on November 9, 2026