Freedcamp now has a hosted Model Context Protocol (MCP) server that plugs your entire Freedcamp workspace — tasks, milestones, time tracking, CRM, wikis, calendar, files, issues, discussions — into Claude Desktop, Claude Code, Cursor, Cline, Continue, Codex CLI, and any other MCP-compatible AI client. 80+ tools, one endpoint, zero install. Full docs and one-line installers live at freedcamp-mcp.surge.sh.

What is Freedcamp MCP?

The Model Context Protocol is the emerging standard that lets AI assistants safely call real tools on your behalf. Freedcamp MCP is a hosted, multi-tenant MCP server that exposes the Freedcamp REST API as a clean catalog of tools your AI can discover and call directly.

Instead of tab-hopping between your AI and Freedcamp, you just ask:

“Create a ‘Fix login race condition’ task in the API project, due Friday, assigned to me, In Progress.”

“Show all tasks I’m assigned to that are overdue, grouped by project.”

“Log 45 minutes against today on the Acme refactor and mark it billable.”

Why it matters

• Hosted, no install. Point your client at the endpoint. No Docker, no cron, no server to maintain.
• Per-user credentials. Each request carries your own Freedcamp API key and secret as headers. Sessions never mix, credentials are redacted from logs, and nothing is persisted to disk.
• One endpoint, every Freedcamp app. Tasks, lists, comments, calendar events, discussions, files, issues, milestones, CRM (tasks and calls), time tracking, wikis, notifications, projects, linked items, favorites, custom fields, and users.
• Stateless and rate-limited. 60 requests per minute per credential pair, TLS end-to-end, HMAC-signed upstream calls.