TimeCamp MCP server

What the model can do

TimeCamp time tracking: time entries in a date range with hours and totals by task and person (people by user id), tasks and projects with budgets, project search, running timers and your own timer; when you ask, can log, edit or delete a time entry, start, stop or discard your timer, and create, rename, move or archive a task.

Reads

• timecamp_time_entriesTimeCamp time entries in a date range (up to 31 days; default the last 7), with hours, task, tags, billable, locked and invoiced…
• timecamp_tasksTimeCamp tasks and projects (a project is a top-level task): name, parent, level, billable, budget and external id.
• timecamp_search_projectsSearch TimeCamp's project tree by name (2+ characters) or by the user ids directly assigned…
• timecamp_running_timersTimers running now in TimeCamp for the people this user can see: user id, task id and when each started (timecamp_tasks names the task…
• timecamp_my_timerWhether the connected TimeCamp user's own timer is running, on which task, since when and for how long.

Acts, when you ask

These change something in TimeCamp. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• timecamp_create_time_entryLogs a time entry in TimeCamp on a date, for the token's user unless assigned_user_id names someone else (that needs admin rights).
• timecamp_update_time_entryEdits a TimeCamp time entry (date, times, duration, task, billable or description); only what is passed changes.
• timecamp_delete_time_entryPermanently deletes a TimeCamp time entry; its hours leave every report.
• timecamp_start_timerStarts the connected TimeCamp user's timer, on a task if given.
• timecamp_stop_timerStops the connected TimeCamp user's running timer (or the timer id given) and saves the tracked time as an entry.
• timecamp_discard_timerCancels the connected TimeCamp user's running timer (or the timer id given) without saving any time; the tracked time is lost.
• timecamp_create_taskCreates a task in TimeCamp, under parent_id or as a new top-level project, optionally billable, with a budget and the user ids who may track on it.
• timecamp_update_taskRenames a TimeCamp task, moves it under another parent, changes its note or external id, or archives (archived true) or restores it…

Connect it

First connect TimeCamp on Dashboard → Connections, then add Memtro to your client once. The TimeCamp tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared TimeCamp connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › How many hours were logged on each project this week?
• › Which entries from the last two weeks are billable but not invoiced?
• › Who has a timer running right now?
• › What budget does the Website rebuild project have?
• › Start my timer on the Client onboarding task.

Questions

Is this an official TimeCamp MCP server?

No. It is Memtro's MCP server with Memtro's TimeCamp connector behind it: the connector reads TimeCamp through its API with the credentials you connect on Dashboard → Connections, and TimeCamp publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in TimeCamp?

Only when you ask, and only what it has been granted: log a time entry; edit a time entry; delete a time entry; start your timer on a task; stop your running timer and save the time; discard your running timer; create a task or project; rename, move or archive a task. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server