TimeCamp

This TimeCamp MCP Server lets you connect an MCP client to a hosted TimeCamp integration, enabling you to create and manage time entries, fetch tasks, and retrieve time data through simple MCP commands. It runs in TypeScript for compatibility with Cloudflare Workers and is designed to be easy to use without local installation. You get a hosted endpoint and practical client configurations to start integrating TimeCamp right away.

How to use

You interact with the MCP server through an MCP client. Begin by connecting to the hosted endpoint or by using the local proxy configuration if your client supports it. The server exposes a set of time-tracking actions you can perform, such as creating a new time entry, listing time entries for a date range, fetching available TimeCamp projects and tasks, deleting an entry, or updating an existing one. To get started, fetch your TimeCamp tasks first so your client can match tasks to time entries, then create entries with notes and optional task assignments as you complete each task.

Common workflow examples include: 1) fetch tasks to understand available projects and tasks; 2) create a time entry with a start and end time, a short note, and an optional task; 3) list time entries for a specific date range to review your work; 4) update an entry if you need to change its time, note, or task association; 5) delete an entry if needed.

How to install

Prerequisites: you need Node.js and a package manager like npm or pnpm. You will connect to the hosted MCP server or run a lightweight local proxy if your workflow requires it. The hosted endpoint is ready to use after you set up your client configuration.

Install and run steps: 1) Prepare your MCP client configuration to point at the hosted endpoint. 2) If you prefer a local proxy, ensure you have the appropriate CLI tool installed (for example, via npm or pnpm). 3) Test the connection with your MCP client using the provided URL or the local proxy URL.

If you deploy a local proxy, use the deployment workflow specified by your tooling, ensuring the final start command is reachable by your client. For the hosted setup, your client will connect to the provided hosted URL without requiring local server startup.

Additional sections

Hosted endpoint: https://my-mcp-server.timecamp-s-a.workers.dev
Client connection examples include a local proxy approach using npx mcp-remote and a direct URL for the hosted endpoint. When connecting from Claude Desktop, you can configure the timecamp MCP server with the following setup to enable remote access through the mcp-remote proxy.

{
  "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 <auth-token>"
      }
    },
    "timecamp_url": {
      "url": "https://my-mcp-server.timecamp-s-a.workers.dev/sse",
      "headers": {
        "Authorization": "Bearer <auth-token>...."
      }
    }
  }
}

Notes on security and usage

Treat the Authorization header as a sensitive credential. Do not commit your token to source control and rotate tokens regularly according to your security policy.

If you encounter issues with your local Claude Desktop setup, refer to the troubleshooting note for specific environments where transport may close unexpectedly.

Not yet implemented

OAuth bearer authorization support and related authentication flow are not yet implemented for this MCP server.

Available tools

add_timecamp_time_entry

Create a new TimeCamp time entry with start time, end time, a note, and an optional task assignment.

get_timecamp_time_entries

Retrieve time entries for a specified date range from TimeCamp.

get_timecamp_tasks

Fetch all available TimeCamp projects and tasks to match against entries.

delete_timecamp_time_entry

Delete a specific time entry by its ID.

update_timecamp_time_entry

Update an existing time entry's time, note, or task assignment.