timesheets-mcp
Verified Safeby owen-lacey
Overview
Manages timesheet entries, activities, responsibilities, competencies, and evidence using Notion databases through a Model Context Protocol (MCP) server.
Installation
npm startEnvironment Variables
- NOTION_API_KEY
- TIMESHEETS_DB_ID
- ACTIVITIES_DB_ID
- RESPONSIBILITIES_DB_ID
- TOPICS_DB_ID
- COMPETENCIES_DB_ID
- EVIDENCE_DB_ID
Security Notes
The server correctly loads API keys and database IDs from environment variables, preventing hardcoding of secrets. Input validation is performed using Zod schemas, mitigating risks from malformed inputs. There are no direct usages of `eval` or other obvious dynamic code execution vulnerabilities within the provided application code. Network interactions are confined to the Notion API via `node-fetch`. The server runs as a `StdioServerTransport` for MCP, implying it's not directly exposed to the network as an HTTP server, reducing external attack surface. Error handling includes catching and returning messages, which is good; however, Notion API errors might occasionally expose some internal details if not sanitized further by a wrapper.
Similar Servers
tempo-mcp-server
Manages Tempo worklogs in Jira via a Model Context Protocol (MCP) server, allowing time tracking and worklog operations through MCP-compatible clients.
better-notion-mcp
Provides a Markdown-first MCP server for Notion, optimizing Notion API interactions for AI agents by consolidating endpoints into composite actions and reducing LLM token overhead for tool descriptions.
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.
notion-automation-suite
Automate Notion workflows by encapsulating specific business rules for different database types (Work, Studies, Personal, Youtuber) and exposing them as Model Context Protocol (MCP) tools for AI agents.