tempo-mcp-server
Verified Safeby ivelin-web
Overview
Manages Tempo worklogs in Jira via a Model Context Protocol (MCP) server, allowing time tracking and worklog operations through MCP-compatible clients.
Installation
npx -y @ivelin-web/tempo-mcp-serverEnvironment Variables
- TEMPO_API_TOKEN
- JIRA_API_TOKEN
- JIRA_EMAIL
- JIRA_BASE_URL
- JIRA_AUTH_TYPE
- JIRA_TEMPO_ACCOUNT_CUSTOM_FIELD_ID
Security Notes
The server uses Zod for robust input validation on all tool parameters and environment variables, mitigating common injection risks. Sensitive API tokens and credentials are strictly sourced from environment variables, preventing hardcoding. Authentication for Jira supports both basic (email:token) and bearer (OAuth 2.0) methods securely. Error handling logs details internally and returns user-friendly messages to the client, limiting information exposure. No 'eval' or obvious obfuscation patterns were found.
Similar Servers
backlog-mcp-server
Integrate Backlog API with AI agents (e.g., Claude) to manage projects, issues, wikis, and Git repositories through natural language commands.
mcp-github-project-manager
AI-powered GitHub Project Management, including automated roadmap generation, sprint planning, issue triaging, task breakdown, and comprehensive project workflow automation.
mcp-http-agent-md
This server provides a Minimal Model Context Protocol (MCP) HTTP server for managing AI agent projects, structured tasks, and versioned history, enabling subagent orchestration and document management.
harvest-mcp-server
Provides a Model Context Protocol (MCP) server for seamless integration with the Harvest time tracking API, enabling AI clients to manage time entries, projects, clients, users, expenses, invoices, estimates, and reports.