TrackVia has a Model Context Protocol (MCP) server that lets AI assistants — like Claude — talk to your TrackVia account directly, using plain-language requests instead of custom code or a separate automation platform.
What is MCP?
Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools and data sources. Any "MCP-aware" client — Claude Code, Claude Desktop, or another MCP-compatible assistant — can connect to the TrackVia MCP server and work with your account's apps, views, records, and files on your behalf.
What it does
Point an MCP-aware client at the server, pass through a TrackVia access token, and your model can work directly against your TrackVia apps — reading and writing records, managing files, running bulk workflows, importing data, finding duplicates, building reports, and more, all through natural-language requests.
Highlights:
- ~60 tools available out of the box
- Runs over Streamable HTTP
- Bring-your-own-token — you authenticate with your own TrackVia access token; TrackVia doesn't issue or store separate MCP credentials
What you can do with it
The server's tools are organized into the following categories:
| Category | What it covers |
|---|---|
| Apps | List apps, look up by name, or fetch a single app by id. |
| Users | List account users, create one, bulk-invite many, or batch-resolve by email. |
| Views | List views, filter by name, page through records, run keyword search. |
| Records | Read, create (single or batch), update, or delete records — including bulk delete within a view. |
| Files | Download, upload, or delete files attached to record fields. |
| Inspect | Annotate a view, record, or whole account with field metadata; export an app's full schema. |
| Query | Filter, sort, select, and export records — evaluated inside the MCP server. |
| Workflows | Upsert by a unique field, or bulk-update / bulk-delete by filter (with preview, backup, and safety confirm). |
| Compose | Duplicate records, copy between views, and expand relationships inline. |
| Resolver | Turn human names (view, field, user) into the right ids. |
| Discovery | Locate fields across views and walk a relationship graph around any record. |
| Profile | Find and merge duplicates, and surface records missing required fields. |
| Ingest | Dry-run or execute CSV / JSON imports with casting and optional upsert. |
| Aggregation | Group-by, pivot, trend, and top-N — computed client-side over paginated records. |
| State machines | Status-field transitions with optimistic-concurrency checks, plus a bulk "advance workflow" variant. |
| Server | Inventory every registered tool with version and status — useful for discovery from the model itself. |
For the full list of individual tools, see [TrackVia MCP Server: Tool Reference]. For setup steps, see [Setting Up the TrackVia MCP Server].
When to use this vs. Zapier, Workato, or the direct API
The MCP server is a good fit when you want to work with your TrackVia data conversationally through an AI assistant — asking questions, running one-off cleanups, or exploring your account's structure — rather than building a standing automation. If you need scheduled, always-on automations between TrackVia and other business apps, Zapier or Workato are still the right tools. If you're writing your own application code, the TrackVia API directly is the better fit.
Comments
0 comments
Please sign in to leave a comment.