← Explore all mcp servers

TRACE REVIEW / Arize AI

Phoenix Remote MCP

Beta MCP endpoint built into Phoenix 19 or later. The root licence forbids offering Phoenix as a hosted service.

“Connect AI assistants directly to your Phoenix instance through the MCP endpoint built into the Phoenix server …”

01 / THE REASONING

Why this made the selection.

  • The publisher documents an MCP endpoint on the Phoenix server for searching projects, traces, datasets, experiments, prompts and annotations.
  • The same page says the endpoint requires Phoenix 19.0.0 or later and that the older npm package is in maintenance mode.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • docs/phoenix/integrations/remote-mcp.mdx
  • LICENSE
  • 2026-10-14 reread of retained pinned setup/configuration evidence for the specific operational details added in this batch.

Our findings

  • The licence text opened at this commit is Elastic License 2.0 and includes the hosted-or-managed-service limitation.
  • The doc’s default code-mode surface includes execute. The page says filesystem, network and subprocess access are blocked inside Monty, with a 30-second code cap.
  • Pinned guide distinguishes OAuth audience scope, server-side master/code-mode switches and the separate evaluator control. The publisher recommends px CLI for most coding-agent workflows; the remote endpoint is useful for ad hoc IDE access.

Not established by this review

  • Phoenix was not installed. No login, trace query or execute call was made. The Apache-2.0 npm package was not reviewed beyond the maintenance sentence in this doc.
  • No authenticated session, installation, permission bypass or package-to-source parity test was performed.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

claude mcp add --transport http phoenix http://localhost:6006/mcp

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Run a Phoenix instance you are allowed to operate, at version 19.0.0 or later.
  2. The command above is the page's Claude Code line for a local Phoenix at http://localhost:6006; replace that base URL with your instance and log in through /mcp in Claude Code. Do not treat this catalogue entry as a hosted Phoenix service. It was not run, and this review did not connect.

Before you start

  • A Phoenix 19 or later instance you operate
  • OAuth or a Phoenix API key if that instance requires authentication

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "phoenix": {
      "url": "http://localhost:6006/mcp"
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/Arize-ai/phoenix/blob/91ea995e0a8db1ac8b67aa2aced89ca29c722c35/docs/phoenix/integrations/remote-mcp.mdx

    Supports: summary, upstreamDescription, install, limitations, access, configExample, bestFor, review, compatibility, transports

  2. Elastic License 2.0 ↗Checked

    https://github.com/Arize-ai/phoenix/blob/91ea995e0a8db1ac8b67aa2aced89ca29c722c35/LICENSE

    Supports: license

Evidence & Ask