add_timecamp_time_entryLABSCO SUMMARY
A week of scribbled notes, turned into a filled timesheet.
The tools are shaped around the thing everyone puts off: paste the list of what you did, have each line matched to a real TimeCamp task, and write the entries in. Reading and editing what is already there means you can fix Tuesday rather than starting the week again.
What it is
A hosted server over the TimeCamp API that creates, reads, edits and deletes time entries, and lists the projects and tasks they attach to.
What you get
- Time entries created with start time, end time, note and an optional task
- Existing entries pulled back for any date range
- The full list of TimeCamp projects and tasks, so entries land on the right one
- An entry's time, note or task assignment updated in place
- Entries deleted by ID
Requirements
A TimeCamp API token, sent as a bearer token. The hosted instance runs at my-mcp-server.timecamp-s-a.workers.dev; clients without remote-server support connect through mcp-remote. Running your own copy means pnpm and a Cloudflare Workers deploy.
Setup effort
Paste a URL with a key — add the endpoint to your client
USE CASES
01
Filling in a timesheet from your notes
Fetch the task list first so each line matches a real project, then write the entries with start and end times.
02
Fixing an entry logged against the wrong project
Pull the day back, then change the task assignment on the one entry instead of deleting and re-entering it.
03
Checking what you booked before invoicing
Read the entries for the billing period and see the notes attached to each one.
04
Removing a duplicate
Delete the entry by ID once you have found which of the two is the stray.
05
Finding which task an activity belongs to
The project and task list is the map — search it before inventing a name that will not match.
5 tools
Listed in project docs. Your client may show a different list.
get_timecamp_time_entriesget_timecamp_tasksdelete_timecamp_time_entryupdate_timecamp_time_entryBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
- npx on PATH
- AUTH_HEADER in your environment
Where it runs
Both documented clients connect to a hosted endpoint.
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://my-mcp-server.timecamp-s-a.workers.dev/sseMCP Clients
Claude Desktop — mcp-remote
CLAUDE DESKTOP — MCP-REMOTE · JSON
{
"mcpServers": {
"timecamp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://my-mcp-server.timecamp-s-a.workers.dev/sse",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer <YOUR_AUTH_TOKEN>"
}
}
}
}Any MCP client — remote URL
ANY MCP CLIENT — REMOTE URL · JSON
{
"mcpServers": {
"timecamp_url": {
"url": "https://my-mcp-server.timecamp-s-a.workers.dev/sse",
"headers": {
"Authorization": "Bearer <YOUR_AUTH_TOKEN>"
}
}
}
}
