English Français العربية

io.github.chrischall/tempo-api-mcp

Registre officiel IA et agents

Tempo time-tracking for Claude — worklogs, plans, and timesheet approvals

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package tempo-api-mcp
Claude Code 
claude mcp add tempo-api-mcp -e 'TEMPO_API_TOKEN=<your tempo_api_token>' -- npx -y tempo-api-mcp@3.2.6
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "tempo-api-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "tempo-api-mcp@3.2.6"
            ],
            "env": {
                "TEMPO_API_TOKEN": "<your tempo_api_token>"
            }
        }
    }
}

Variables d'environnement

  • TEMPO_API_TOKEN obligatoire secret Your Tempo API token (Settings → API integration in your Tempo workspace)

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

tempo-api-mcp

Tempo API MCP server for Claude — developed and maintained by AI (Claude Code)

Confirmations

Every write (create/update/delete, and the timesheet submit/approve/reject/reopen/recall actions) asks the user to confirm before it changes anything: a confirmation prompt where the client supports one; otherwise the first call returns a preview of exactly what would be sent plus a confirmToken, and only a repeat call with that token proceeds.

variabledefault
MCP_CONFIRM_MODEask-userWhat a write does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). ask-user: two steps — the first call does nothing and returns a preview plus a token, and the model must get your approval in chat before calling again with it. auto: the same two steps, but the model may use the token after reviewing the preview itself. refuse: writes are refused on such clients. A client that can show prompts (Claude Code) gets the real prompt unless MCP_CONFIRM_ELICITATION=off. An unrecognised value is treated as refuse.
MCP_CONFIRM_ELICITATIONonoff never shows a confirmation prompt, so every client gets the MCP_CONFIRM_MODE two-step flow. Set it for opencode v2: it claims to support prompts but never displays them, so writes (including timesheet approvals) hang. Any other value stays on.
MCP_CONFIRM_TTL_SECONDS600How long a token stays valid.
MCP_CONFIRM_SECRETrandom per processSigning key; set it only if tokens must survive a server restart.

In opencode, set it in the server's environment block:

{
  "mcp": {
    "servers": {
      "tempo": {
        "type": "local",
        "command": ["npx", "-y", "tempo-api-mcp"],
        "environment": { "TEMPO_API_TOKEN": "…", "MCP_CONFIRM_ELICITATION": "off" }
      }
    }
  }
}

Questions fréquentes

Qu'est-ce que io.github.chrischall/tempo-api-mcp ?

Tempo time-tracking for Claude — worklogs, plans, and timesheet approvals

Comment installer io.github.chrischall/tempo-api-mcp ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add tempo-api-mcp -e 'TEMPO_API_TOKEN=<your tempo_api_token>' -- npx -y tempo-api-mcp@3.2.6. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.chrischall/tempo-api-mcp ?

Oui. Il attend TEMPO_API_TOKEN, à renseigner dans sa configuration.

io.github.chrischall/tempo-api-mcp est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.github.chrischall/tempo-api-mcp ?

Il est publié par chrischall. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.