Arize Tracing Assistant
Overview
This legacy MCP server provides documentation and examples for instrumenting AI applications with Arize AX. It has been superseded by the Arize AX MCP Server, a hosted remote server that connects with an endpoint URL and an Arize API key and needs no local installation. For maintained Arize AX workflows, install and use Arize Skills.
Legacy installation
Install uv
Make sure uv - the fast Python package manager - is installed on your system. Installation instructions: uv installation guide.
-
On macOS:
pip install uv
or
brew install uv
-
On Linux:
curl -LsSf https://astral.sh/uv/install.sh | less
-
On Windows:
powershell -c "irm https://astral.sh/uv/install.ps1 | more"
IDE integration
Antigravity
- Open the MCP Store panel within the "..." dropdown at the top of the editor's side panel.
- Type "Arize" in the search and click Install.
OR
- To Install as a Custom MCP Server, Click on "Manage MCP Servers"
- Click on "View raw config"
- Add the following code to your mcp_config.json:
"mcpServers": {
"arize-tracing-assistant": {
"command": "uvx",
"args": [
"arize-tracing-assistant@latest"
]
}
}
Cursor
- Go to Cursor Settings -> MCP.
- Click "Add new global MCP server" and add the server to your config JSON.
- Remove the
envsection if you don't have access to RunLLM.
Example config:
"arize-tracing-assistant": {
"command": "uvx",
"args": [
"arize-tracing-assistant@latest"
]
}
Claude Desktop
- Go to Claude Desktop Settings.
- In Developer > Edit Config and add this to your config JSON:
"arize-tracing-assistant": {
"command": "/Users/myuser/miniconda3/bin/uvx",
"args": [
"arize-tracing-assistant@latest"
]
}
Manual MCP config
Add the following snippet to your MCP config file:
"mcpServers": {
"arize-tracing-assistant": {
"command": "uvx",
"args": [
"arize-tracing-assistant@latest"
]
}
}
CLI Integration
Gemini CLI
Install using the Gemini CLI extension:
gemini extensions install https://github.com/Arize-ai/arize-tracing-assistant
Usage
Once the MCP server is running, ask your IDE or LLM questions about tracing or general Arize support like...
- Instrument this app using Arize
- Can you use manual instrumentation so that I have more control over my traces?
- How can I redact sensitive information from my spans?
- Use decorators to have more control over the span attributes
- Can you make sure the context of this trace is propagated across these tool calls?
- Where can I find my Arize keys?
Troubleshooting
-
Make sure the JSON configs are perfectly formatted.
-
Clear the uv cache with
uv cache cleanto force accessing the latest version. -
Make sure your
uvcommand is pointing to the right location by runningwhich uv, or simply use the full path. -
The server should start in the terminal just by running:
uvx arize-tracing-assistant@latest -
Use the Anthropic MCP inspector by running:
npx @modelcontextprotocol/inspector uvx arize-tracing-assistant@latest
Metadata
Release files for arize-tracing-assistant 0.3.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| arize_tracing_assistant-0.3.9.tar.gz | 53.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| arize_tracing_assistant-0.3.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 147.1 kB
Release files / arize_tracing_assistant-0.3.9.tar.gz
| Download URL | arize_tracing_assistant-0.3.9.tar.gz |
|---|---|
| Size | 53.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0dd1212fe98c8dea393a26c8a5735fee2924b46e3ae75d3b0a2c638feea14988
|
|
BLAKE2b-256 checksum How to use checksums |
6ded2bc2d13378566578a41265699b7260ec08b44c6c4fa4878428cf9efa0c35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency logRelease files / arize_tracing_assistant-0.3.9-py3-none-any.whl
| Download URL | arize_tracing_assistant-0.3.9-py3-none-any.whl |
|---|---|
| Size | 93.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26a8c6fcab09e2e3fa5f570b7fd79e4689b08bd40064eda23a790bd2f808cdb5
|
|
BLAKE2b-256 checksum How to use checksums |
d5b30e95b2a7933adfd5ab55ada78ab1547ac5bdc42b53d223e5fbd27e794764
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency log