Tempo time-tracking for Claude — worklogs, plans, and timesheet approvals
Tempo time-tracking for Claude — worklogs, plans, and timesheet approvals
This is a well-structured MCP server for the Tempo API with strong input validation and deliberate path-traversal defenses. The code demonstrates good security practices including regex-based constraints on identifiers interpolated into URLs, proper use of schema validation via Zod, and clear separation between read-only and write operations. Permissions align well with the server's stated purpose of providing Tempo API access. No credentials are hardcoded, and authentication is delegated to the client layer. Minor code quality observations exist but do not constitute security concerns. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 1 high severity). Package verification found 1 issue.
7 files analyzed · 6 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: TEMPO_API_TOKEN
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-chrischall-tempo-api-mcp": {
"env": {
"TEMPO_API_TOKEN": "your-tempo-api-token-here"
},
"args": [
"-y",
"tempo-api-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.