Skip to main content

MCP Authentication

  • Updated

Connect Claude, ChatGPT, Gemini/Antigravity, Perplexity, or Microsoft Copilot to your TrackVia account

1. Getting Started

What you'll need

  • An active TrackVia account with whatever role and permissions you normally use — the assistant can only do what your TrackVia login is already allowed to do, nothing more.
  • One of the supported AI assistants: Claude (claude.ai, Claude Desktop, or Claude Code), ChatGPT (Business, Enterprise, or Edu plan with Developer Mode), or Microsoft Copilot Studio (a System Administrator for Power Platform may be needed to provision the server).
  • The TrackVia MCP server address (below).
  • For the command-line / machine-to-machine path only: a TrackVia Super Admin who can set up a dedicated service-account user and issue it an access token.

Installation overview

AI clients provide various ways to register connections with MCP servers. These may include:

  • A user interface in a web or desktop application
  • Commands to execute in a terminal
  • A file to edit

Check your AI client's documentation for the MCP server registration options it provides. If you register an MCP server with a local client, the client typically stores the registration in a file on your machine — exact paths and formats (JSON, TOML, and others) vary by client, and some clients support environment variables instead.

Connection details

Field Value
Server address https://mcp.trackvia.com/mcp
Authentication OAuth 2.0 — sign in with your normal TrackVia username and password
Transport Streamable HTTP

All the assistants below connect the same way under the hood: you give the assistant the server address above, and the first time you use it you're sent through a standard browser sign-in screen hosted by TrackVia, where you log in with your existing TrackVia credentials. Once you approve the connection, the assistant holds a short-lived access token — TrackVia doesn't hand out separate passwords or long-lived API keys for this path.

Find your assistant

Jump to your assistant:

Start Here If You Use Claude

Claude.ai or Claude Desktop

  1. Go to Settings → Connectors. (On a Team or Enterprise plan, an Owner or Primary Owner admin is required to add the connector under Organization Settings → Connectors — after that, each person connects individually from their own Settings → Connectors. Individual plans [Free, Pro, Max] allow any user to add a custom Connector.)
  2. Select "Add custom connector."
  3. Enter the server address: https://mcp.trackvia.com/mcp
  4. Select "Add," then "Connect." You'll be sent to TrackVia's sign-in page to log in and approve access.
  5. Turn the connector on for a conversation from the tools ("+") menu.

Claude Code (the command line tool)

If you use Claude Code instead of the Claude web or desktop app, connect from your terminal. Register the server:

 
claude mcp add --transport http trackvia https://mcp.trackvia.com/mcp

Then run /mcp inside a session, select trackvia, and choose Authenticate. A browser window opens for you to sign in and approve access — the same sign-in step as the Claude.ai flow above.

Additional Resources:

Start Here If You Use ChatGPT

Custom connectors in ChatGPT currently require a Business, Enterprise, or Edu plan with Developer Mode turned on.

  1. Turn on Developer Mode: Settings → Apps & Connectors → Advanced Settings. (Enterprise/Edu admins can also grant this via Permissions & Roles.)
  2. Go to Settings → Apps & Connectors → Create.
  3. Enter the server address: https://mcp.trackvia.com/mcp
  4. When prompted for authentication, sign in with your TrackVia credentials.
  5. Select "Scan Tools," then "Create."

Additional Resources:

Unverified for this beta

If ChatGPT can't discover the authentication endpoints automatically, it will ask for a manually issued Client ID and Secret. We recommend creating a dedicated service account for the MCP server to use, with scoped roles and permissions, and issuing an API token for that service account.

Start Here If You Use Microsoft Copilot (Copilot Studio)

This integration is built through Copilot Studio's agent tools, so you'll need Copilot Studio maker access.

  1. Open the Tools page for your agent, then select Add a tool → New tool → Model Context Protocol.
  2. Enter a name and description for the connector, and the server address: https://mcp.trackvia.com/mcp
  3. Under authentication, choose OAuth 2.0 → Dynamic Discovery first.
  4. Create the connection and add it to your agent.

Additional Resources:

Unverified for this beta

If Copilot Studio can't discover the authentication endpoints automatically, it will ask for a manually issued Client ID and Secret. We recommend creating a dedicated service account for the MCP server to use, with scoped roles and permissions, and issuing an API token for that service account.

Start Here If You Use Google Gemini

Google Gemini users must have Gemini Enterprise - Business edition to connect to a server.

  1. Sign in to Gemini Enterprise - Business edition.
  2. Click Settings & help.
  3. Select your Team, then navigate to Manage team → Connected Apps.
  4. In the Connected Apps page, click "Add MCP Server" and follow the instructions.

Additional Resources:

Start Here If You Use Google Antigravity

Confirmed via the Antigravity command-line client and the Antigravity desktop app. Google Gemini users must have Gemini Enterprise - Business edition to connect to a server.

  1. In your Antigravity chat, ask it to connect: "Connect to the TrackVia MCP server at https://mcp.trackvia.com/mcp using OAuth."
  2. A browser window opens to TrackVia's sign-in page.
  3. Log in with your TrackVia username and password (or your organization's SSO) and select Authorize.
  4. Return to Antigravity — it confirms the connection, and your TrackVia tools are ready to use.

Additional Resources:

Start Here If You Use Perplexity

Requires a Perplexity Pro, Max, or Enterprise plan — custom connectors aren't available on the free tier.

  1. In Perplexity, select your profile (bottom left) → Settings → Connectors.
  2. Select "+ Custom connector," then "Remote," and give it a name (e.g. "TrackVia").
  3. Enter the server URL: https://mcp.trackvia.com/mcp. Under Transport, select Streamable HTTP.
  4. Expand Advanced, select OAuth 2.0 as the authentication type, and enter a Client ID of your choosing.
  5. Check "I understand custom connectors can introduce risks," then select Add. You'll be sent to TrackVia's sign-in page to log in and approve access.

On Enterprise plans, an admin can instead add the connector once under Enterprise settings → Connectors, scoped to the whole organization rather than to each person individually.

Additional Resources:

Start Here If You Use An AI Tool Not Included In This List

Additional Tools

New tools are being introduced to the market regularly. Amazon Quick, Cursor, and Codex are just three examples of AI tools not included in this initial configuration guide. If your organization uses an approved AI tool that isn't on the current list, reach out to your TrackVia contact to discuss support. While some vendors may work out of the box, some scenarios will need additional configuration from the TrackVia Engineering team.

 

Related Articles

 

Related articles

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk