feat: add SolidTime MCP server for time tracking integration

Implements a Model Context Protocol server that exposes SolidTime's
time tracking API as 22+ tools for use with Claude, Cursor, and other
MCP-compatible clients. Supports stdio and HTTP transport modes,
Docker deployment, and self-hosted SolidTime instances.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Danijel
2026-03-17 23:45:42 +01:00
commit fe432d4a09
30 changed files with 5780 additions and 0 deletions

20
.env.example Normal file
View File

@@ -0,0 +1,20 @@
# =============================================================================
# STDIO MODE (local, via `npm run dev` or `npm start`)
# =============================================================================
# These are read from the server's environment when running in stdio mode.
SOLIDTIME_API_TOKEN=your-api-token-here
SOLIDTIME_ORGANIZATION_ID=your-organization-uuid-here
# Optional — defaults to https://app.solidtime.io
# SOLIDTIME_API_URL=https://your-instance.example.com
# Optional — IANA timezone name for displaying and accepting local times (e.g. Europe/Berlin, America/New_York)
# Without this, all times are shown and expected in UTC.
# SOLIDTIME_TIMEZONE=Europe/Berlin
# =============================================================================
# HTTP MODE (cloud, via `npm run start:http` or Docker)
# =============================================================================
# In HTTP mode, API token and org ID come from MCP client headers,
# NOT from environment variables. Only server-level config goes here.
#
# PORT=3000
# SOLIDTIME_API_URL=https://app.solidtime.io