Integration

TrackVia integration

TrackVia is a low-code database and workflow platform. Find applications, views and users, read, search, create, update and delete records in a view, upload, download and delete the files and attachments stored on record fields, create users, and invoke the account's microservices. The API cannot reach forms, dashboards, filters, flows, tables or account settings, and a microservice invoked by query string only (no body) is not exposed. Authentication combines the account API key (user_key query parameter) with an access token created by a Super Admin for an API user (Bearer header); the token's user decides what is visible. Rate limits: 1,200 calls a minute and 11 million a month.

Connect TrackVia How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in TrackVia.Built from the 20 TrackVia tools below, on the connection you add once.

What you can do with TrackVia

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Record, 4 operations

create_recordCreate recordPOSTCreates a record in a view from field values keyed by exact field names; returns the created record with the view's structure.
delete_recordDelete recordDELETEDeletes one record. This cannot be undone.
get_recordGet recordGETReturns one record of a view by id: structure (the view's fields) and data (the record's field values).
update_recordUpdate recordPUTUpdates a record: send only the fields to change, keyed by exact field names; fields left out keep their value. Returns the updated record.

Attachment, 3 operations

delete_attachmentsDelete attachmentsDELETEDeletes the listed attachments from an attachments field of a record. This cannot be undone.
get_attachmentGet attachmentGETDownloads one attachment of a record and returns it as a file.
upload_attachmentUpload attachmentPOSTUploads one file into an attachments field of a record (the field keeps its other attachments) and returns the record.

File, 3 operations

delete_fileDelete fileDELETEDeletes the file stored in an image or document field of a record. This cannot be undone.
get_fileGet fileGETDownloads the file stored in an image or document field of a record and returns it as a file.
upload_fileUpload filePOSTUploads a file into an image or document field of a record, replacing what the field held, and returns the record.

All, 2 operations

delete_all_attachmentsDelete all attachmentsDELETEDeletes every attachment in an attachments field of a record. This cannot be undone.
delete_all_recordsDelete all recordsDELETEDeletes EVERY record in the view. This cannot be undone; prefer delete_record for single records.

User, 2 operations

create_userCreate userPOSTCreates a user in the account from an email, first name and last name (time zone optional) and returns the new user record.
list_usersList usersGETLists the account's users, one page at a time (start, max). Returns structure (the user fields) and data (one object per user), plus totalCount.

View, 2 operations

list_view_recordsList view recordsGETReads the records of a view, one page at a time: structure lists the view's fields (name, type, required, permissions), data holds the records, totalCount the number of records in the view.
list_viewsList viewsGETLists the views the API user can see, with id, name, application name and default flag; name filters by view name. Pass a view id to the record tools.

App, 1 operation

list_appsList appsGETLists the applications in the account (name and id); name filters by application name.

Find, 1 operation

find_recordsFind recordsGETSearches a view for one term (a contains search over all its records) and returns matching records with the view's structure and totalCount, one page at a time.

Integration, 1 operation

list_microservicesList microservicesGETLists the account's microservices (name and microserviceId). Pass a microserviceId to invoke_microservice.

Invoke, 1 operation

invoke_microserviceInvoke microservicePOSTRuns a microservice with a JSON payload and returns whatever the microservice answers. The microservice's own code decides what it does, so check what it does before calling it.

Use TrackVia from Claude Code, Cursor or Codex

Connect TrackVia in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its TrackVia operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect TrackVia

Create your workspace
Sign up free. Nothing to install.
Connect TrackVia once
Add your TrackVia connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.