Productivity · Remote MCP server
Timesheet
Timesheet.io MCP server - manage timers, projects, tasks and reports.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.timesheetIO/timesheet-mcp- Version
- 2.0.2
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-27
- Updated
- 2026-09-27
- Publisher
- timesheetIO (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/timesheetIO) · how
- Website
- mcp.timesheet.io
- Repository
- github.com/timesheetIO/timesheet-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.timesheet.io | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @timesheet/mcp | 2.0.2 | stdio |
How to connect Timesheet
Timesheet is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.timesheet.io, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @timesheet/mcp version 2.0.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @timesheet/mcp@2.0.2. It reads the environment variable TIMESHEET_API_TOKEN (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"timesheet-mcp": {
"command": "npx",
"args": [
"-y",
"@timesheet/mcp@2.0.2"
],
"env": {
"TIMESHEET_API_TOKEN": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| TimelyMeeting programmes for AI: drafted by your assistant, approved by a person, published as PDF and web. | Remote · HTTPLive check: sign-in required |
| TimequipManage Timequip projects, tasks, comments, members, and dashboards through MCP. | Remote · HTTPLive check: sign-in required |
| TimeraAI Chief of Staff for your time. Drift score, calendar, goals, and AI coaching. | Local · stdio |
| TimergyCreate scheduling polls, vote, and finalize times from AI agents. | Local · stdio |
| TimesheetsTrack billable time from your AI chat: timers, entries, reports, CSV export. All data stays local. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| TimeToPostOfficial TimeToPost MCP server for social post drafting, scheduling, publishing and approval queues. | Remote · HTTPLive check: sign-in required |
| TimeZestMCP server for TimeZest - appointment scheduling, agents, appointment types, and resources for MSPs. | Local · stdio |
| TimeZestMCP server for TimeZest - appointment scheduling, agents, appointment types, and resources for MSPs. | Local · stdio |