HelloTracks for AI agents
HelloTracks is a location-based workforce management platform for dispatching jobs and tracking mobile field teams. Teams use it to keep project work visible instead of tracking it across separate spreadsheets. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in HelloTracks.
Check a job's status
Look up a dispatched job's current status to update a customer on arrival time.
Assign a new job
Create a new field job with a location and details for a technician to pick up.
Archive a job with confirmation
Archive a completed job only after a dispatcher confirms it was closed out correctly.
10 HelloTracks actions, graded by risk.
Every HelloTracks action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
6Look things up. Allowed by default.
- hellotracks.get_jobGet Job
- hellotracks.list_jobsList Jobs
- hellotracks.list_placesList Places
- hellotracks.list_membersList Members
- hellotracks.get_account_contextGet Account Context
- hellotracks.get_current_locationsGet Current Locations
write
2Create and change things. Allow, or ask the user first.
- hellotracks.update_jobUpdate Job
- hellotracks.upsert_jobUpsert Job
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- hellotracks.delete_jobDelete Job
- hellotracks.archive_jobArchive Job
HelloTracks in three steps.
- 01Your users connect HelloTracksThey add their HelloTracks api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “update Job” can wait for the user, and “delete Job” can be denied outright.
- 03Any agent can actYour agent calls HelloTracks through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('hellotracks', { read: 'allow', write: 'ask', // update_job destructive: 'deny', // delete_job }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How HelloTracks connects.
Users add their HelloTracks api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same HelloTracks connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use HelloTracks from any agent.
More project management apps.
HelloTracks and Arc0, answered.
Can I use HelloTracks with Claude, ChatGPT or Cursor?
Yes. Connect HelloTracks to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the HelloTracks actions you allow.
How do users connect HelloTracks?
Users add their HelloTracks api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which HelloTracks actions can my agent take?
10 in total: 6 read, 2 write and 2 destructive, such as “update Job”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in HelloTracks?
Yes. Actions like “delete Job” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call HelloTracks too?
Yes. The same HelloTracks connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug HelloTracks into your agent.
Your users connect HelloTracks once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan