Timen

io.github.vahtelPublished by GitHub account vahtelv1.0.0Updated Oct 24, 2026

Timen time tracking — timers, time entries, reports, projects, and clients.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Timen is a remote MCP server for time tracking, letting an assistant work with timers, time entries, reports, projects and clients.

What you can do
Start, stop and manage timers for tracked work sessions, as implied by the time tracking purpose described in the registry entry. Create and review time entries recorded against work. Generate reports summarizing tracked time. Organize and reference projects and clients that time is logged under. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Useful when you want an assistant to help log working hours, check running timers, or pull time reports and project or client breakdowns without switching to the Timen app.
Requirements
A remote MCP endpoint at mcp.gettimen.com reached over streamable HTTP, with OAuth authentication required. No environment variables or headers are declared. A Timen account is implied by the OAuth sign-in.
Before you install
OAuth grants the assistant access to your Timen workspace, so review the scopes requested at sign-in. The server can likely create and change time entries, timers, projects and clients, so confirm before letting it write or delete records. Time and client data is sent to a third-party service.

Installation

In SourceWeft

  1. Open Timen in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.vahtel%2Ftimen/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "timen": {
      "type": "http",
      "url": "https://mcp.gettimen.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.