Claude Code Integration

What This Provides

TaskTime Pro ships a Claude Code plugin at integrations/claude/tasktime/. It contributes a TaskTime Pro skill and a plugin-managed MCP server that launches the bundled local bridge. Claude Code users do not need to hand-write MCP config when they install the plugin.

This is separate from the OpenClaw/ClawHub bundle. The same TaskTime Pro bridge powers both integrations, but Claude Code uses .claude-plugin/plugin.json, a root marketplace file, and Claude's plugin MCP naming rules.

Install From GitHub

Add the TaskTime Pro marketplace from GitHub, then install the plugin from that marketplace:

/plugin marketplace add https://github.com/tasktimepro/tasktime
/plugin install tasktime@tasktimepro

If Claude Code asks you to reload plugin components, run:

/reload-plugins

Plugin Contents

• Marketplace catalog: .claude-plugin/marketplace.json.
• Plugin manifest: integrations/claude/tasktime/.claude-plugin/plugin.json.
• Skill root: integrations/claude/tasktime/skills/tasktime/SKILL.md.
• MCP server config: integrations/claude/tasktime/.mcp.json.
• Bundled bridge launcher: scripts/run-tasktime-agent-bridge.mjs.
• Bundled bridge binary: vendor/tasktime-agent-bridge.mjs.
• Stable agent identity: tasktime.agent.claude-code, label Claude Code on this device.
• Secret-free bridge status file: tasktime-agent-bridge.status.json beside the plugin launcher; pairing URLs come from setup tools.

Pair TaskTime Pro

After installation, Claude Code starts the plugin MCP server automatically when the plugin is enabled. The server appears as plugin:tasktime:tasktime. The user still opens TaskTime Pro and approves the local bridge in Account > Agent Access before Claude can read or mutate local data.

Plugin-bundled MCP tools use Claude's scoped tool-name form:

mcp__plugin_tasktime_tasktime__list_projects

For pairing recovery, use the plugin bridge's get_pairing_status tool to get the active launch URL. If the pairing code expired or was consumed, call refresh_pairing. Do not pair TaskTime Pro to a separately launched terminal bridge when the plugin already owns the MCP server.

MCP-Only Claude Clients

Claude clients that support MCP but not Claude Code plugins can use the standalone TaskTime Pro bridge package instead. Add an MCP stdio server entry like this:

{
  "mcpServers": {
    "tasktime": {
      "command": "npx",
      "args": [
        "-y",
        "@tasktimepro/agent-bridge",
        "--app-url",
        "https://app.tasktime.pro"
      ]
    }
  }
}

The same pairing and approval model applies: the visible TaskTime Pro browser app must approve Account > Agent Access before tools can operate on local data.

Safety Model

The Claude plugin does not create a cloud API or remote-control channel. It launches a same-device stdio bridge. The paired browser app remains the authority for data validation, mutations, downloads, email sends, sync behavior, restore flows, account deletion, and approval-token verification.

• Use MCP tools before browser UI automation.
• Inspect or preview before write, billing, export, email, restore, or delete actions.
• Keep destructive, restore, billing, export, and email actions explicit and approval-gated.
• Do not directly edit browser storage, Yjs documents, cloud sync files, invoice state, or billing state.

Publishing Path

The GitHub marketplace is the immediate public distribution path. TaskTime Pro can also submit the plugin for Claude Code plugin directory review after running claude plugin validate in an environment with Claude Code installed. Anthropic's official directory is curated separately at Anthropic's discretion.