TimeCamp for AI agents
TimeCamp is a time tracking tool for logging work hours against projects, used by teams that bill clients or monitor project costs by the hour. 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 TimeCamp.
List projects being tracked
Pull the current project list as a read-only check before reporting on hours.
Summarize tracked time by project
Read logged hours for a project to prepare a client billing summary.
Flag a project for review
Surface a project's tracked hours for a manager to review before it's invoiced.
1 TimeCamp actions, graded by risk.
Every TimeCamp action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- timecamp.get_projects_listGet Projects List
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
TimeCamp in three steps.
- 01Your users connect TimeCampThey add their TimeCamp api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls TimeCamp through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('timecamp', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How TimeCamp connects.
Users add their TimeCamp 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 TimeCamp 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 TimeCamp from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
TimeCamp and Arc0, answered.
Can I use TimeCamp with Claude, ChatGPT or Cursor?
Yes. Connect TimeCamp 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 TimeCamp actions you allow.
How do users connect TimeCamp?
Users add their TimeCamp 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 TimeCamp actions can my agent take?
1 in total: 1 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in TimeCamp?
Yes. Allow read actions and deny writes in the TimeCamp policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call TimeCamp too?
Yes. The same TimeCamp connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug TimeCamp into your agent.
Your users connect TimeCamp once, under your brand. Your agent gets 1 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan