Setting Up the TrackVia MCP Server

This article walks through connecting an MCP-aware client (such as Claude Code) to your TrackVia account.

What you'll need

• A TrackVia access token. You get this by exchanging your API user credentials for a short-lived OAuth access token through TrackVia's OAuth flow. See API Authentication and Access if you haven't set up an API user yet.
• An MCP-aware client, such as the Claude Code CLI.

The server speaks MCP over streamable HTTP at the /mcp endpoint. Every MCP request must carry your credentials in the headers described below.

Installation steps

1. Install the Claude Code CLI, if you haven't already.
2. Register the server with your TrackVia access token:

   claude mcp add --transport http trackvia https://mcp.go.trackvia.com/mcp \
     --header "Authorization: Bearer YOUR_TRACKVIA_ACCESS_TOKEN"

3. Optional: pin a specific TrackVia host (this defaults to the server's configured host) and/or target a sandbox account:

   claude mcp add --transport http trackvia https://mcp.go.trackvia.com/mcp \
     --header "Authorization: Bearer YOUR_TRACKVIA_ACCESS_TOKEN" \
     --header "X-TrackVia-Host: mcp.go.trackvia.com/mcp" \
     --header "X-TrackVia-Account-Id: 12345"

4. Verify the connection:

   claude mcp list

TrackVia should appear in the list as connected.

Frequently asked questions

Where do I get a TrackVia access token? From your TrackVia account — exchange your API user credentials for a short-lived OAuth access token through TrackVia's OAuth flow.

Are my credentials stored anywhere? No. Access tokens are extracted from request headers, used for the outbound TrackVia call, and then discarded — they aren't stored on the server. The server's logger also redacts credential fields so they're never written to logs.

Related articles

• Introduction to the TrackVia MCP Server
• TrackVia MCP Server: Tool Reference
• TrackVia MCP Server: Example Prompts and Workflows
• TrackVia MCP FAQ
• API Authentication and Access