Tempo MCP Server

Created By
ivelin-weba year ago
MCP server for managing Tempo worklogs in Jira
Overview

what is Tempo MCP Server?

Tempo MCP Server is a Model Context Protocol (MCP) server designed for managing Tempo worklogs in Jira, providing tools for tracking time and managing worklogs through Tempo's API.

how to use Tempo MCP Server?

You can use the server via NPX without installation or by cloning the repository for local development. For NPX, run the command with your API tokens and Jira details. For local usage, configure the wrapper script with your credentials and run it.

key features of Tempo MCP Server?

  • Retrieve worklogs for specific date ranges
  • Create, edit, and delete worklogs
  • Bulk create multiple worklogs in one operation
  • Integration with MCP-compatible clients like Claude and Cursor

use cases of Tempo MCP Server?

  1. Logging time against Jira issues for project management
  2. Bulk updating worklogs for multiple tasks
  3. Integrating with other tools for enhanced productivity

FAQ from Tempo MCP Server?

  • What are the system requirements?

Node.js 18+, a Jira Cloud instance, and API tokens for Tempo and Jira are required.

  • Is there a recommended way to use the server?

Yes, using NPX is recommended for most users for ease of use.

  • How can I troubleshoot issues?

Check environment variables, API token permissions, and use the inspector for debugging.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ivelin-web
Star
6
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago