ManicTimeMcp 0.2.40

ManicTime MCP

A .NET MCP server and Repl-based command app that gives AI agents and local operators read-only access to local ManicTime activity data: applications, documents, websites, screenshots, and usage patterns.

Compatibility notice — This project is an independent integration and is not affiliated with or endorsed by ManicTime or Finkit.

Three aligned modes

The same application exposes three aligned surfaces:

When to use which mode

• Use MCP when Claude, Copilot, Codex, or another MCP-compatible client should call the server over stdio.
• Use CLI when you want one direct command locally, especially for testing payloads or troubleshooting output.
• Use REPL when you want interactive discovery, --help, or to explore routes before wiring an MCP client.

Launching the app

Published package

Requires the .NET 10+ SDK. Run directly with dnx:

dnx -y ManicTimeMcp mcp serve

This downloads the latest published package and starts the MCP server over stdio.

Local development

Start the MCP server from source:

dotnet run --project src/ManicTimeMcp/ManicTimeMcp.csproj -- mcp serve

Run one CLI command directly:

dotnet run --project src/ManicTimeMcp/ManicTimeMcp.csproj -- timeline list --output:json

Start the interactive REPL:

dotnet run --project src/ManicTimeMcp/ManicTimeMcp.csproj

dotnet run requires the -- separator because it splits dotnet launcher arguments from the app's own command path. MCP client JSON configs do not use this separator because they already pass arguments as an explicit array.

Agent configuration

Visual Studio / VS Code (Copilot)

The package embeds a .mcp/server.json manifest. Browse ManicTimeMcp on NuGet.org, open the MCP Server tab, and copy the generated configuration into your IDE.

Or add manually to .vscode/mcp.json:

{
  "servers": {
    "manictime-mcp": {
      "type": "stdio",
      "command": "dnx",
      "args": ["-y", "ManicTimeMcp", "mcp", "serve"]
    }
  }
}

Claude Code

claude mcp add manictime-mcp -- dnx -y ManicTimeMcp mcp serve

Claude Desktop

Add to claude_desktop_config.json (%APPDATA%\Claude\claude_desktop_config.json):

{
  "mcpServers": {
    "manictime-mcp": {
      "command": "dnx",
      "args": ["-y", "ManicTimeMcp", "mcp", "serve"]
    }
  }
}

OpenAI Codex CLI

codex mcp add manictime-mcp -- dnx -y ManicTimeMcp mcp serve

Generic MCP JSON configuration

{
  "mcpServers": {
    "manictime-mcp": {
      "command": "dnx",
      "args": ["-y", "ManicTimeMcp", "mcp", "serve"],
      "transportType": "stdio"
    }
  }
}

Repl-first surface

Commands and MCP tools

Resources

Prompts

Workspace and screenshot save workflow

screenshot save writes only inside MCP client roots.

• If the MCP client supports native roots, screenshot save uses them directly.
• If the client does not support native roots, call workspace init {path} first to establish soft roots for the session, then call screenshot save.
• workspace init is a session-scoped MCP helper. It exists mainly for agent workflows, not as a replacement for local filesystem paths in CLI mode.

See docs/modes-and-workspaces.md for end-to-end examples.

Supported scope

• Supported: ManicTime Windows desktop with local storage (ManicTimeReports.db).
• Not supported (v1): ManicTime Server deployments, non-Windows clients, server-centric collectors.
• Transport: stdio only.

Building from source

dotnet restore src/ManicTimeMcp.slnx
dotnet build src/ManicTimeMcp.slnx -warnaserror
dotnet test --solution src/ManicTimeMcp.slnx
dotnet pack src/ManicTimeMcp.slnx -c Release

See getting-started.md for prerequisites and local usage, and AGENTS.md for engineering rules.

Contributing

1. Read spec/README.md for workstream specifications.
2. Pick a workstream and implement only that scope.
3. See AGENTS.md for build commands, quality rules, and constraints.

License

MIT