概要
What is FreeloMCP?
FreeloMCP is an unofficial community-built Model Context Protocol (MCP) server that provides 104 tools covering 100% of the Freelo API v1. It enables AI assistants (like Claude Desktop, Claude Code, Cline, and others) to interact with Freelo, a Czech project management and task-tracking service.
How to use FreeloMCP?
Install and run via npx (recommended) or clone the repository. Configure your MCP client (e.g., Claude Desktop) by adding a mcpServers entry with the command npx -y freelo-mcp and environment variables FREELO_EMAIL, FREELO_API_KEY, and FREELO_USER_AGENT. Restart the client and verify by asking to list your Freelo projects.
Key features of FreeloMCP
- 104 MCP tools covering 100% of Freelo API v1
- Fully tested: 207 unit tests + 82 real API tests
- Smart filtering with pagination and advanced filters
- HTTP Basic Authentication with API key
- Token limit fixes for large datasets
- MCP Annotations with automatic behavioral hints
- Modular architecture organized in 19 modules
- Supports Stdio, Streamable HTTP, and SSE transports
Use cases of FreeloMCP
- Manage tasks, subtasks, and task lists from an AI chat
- Create, update, and archive projects using natural language
- Track time, upload files, and manage comments on tasks
- Search across projects with full-text Elasticsearch
- Automate invoice generation and work report management
FAQ from FreeloMCP
Is FreeloMCP an official Freelo product?
No, this is an unofficial community project and is not directly supported by Freelo.
What runtime or dependencies are required?
Node.js is required. The server is published as an npm package and can be run via npx without local installation.
How does authentication work?
Authentication uses HTTP Basic Authentication with a Freelo API key. You must provide FREELO_EMAIL and FREELO_API_KEY as environment variables.
Where does my data live?
All data remains on Freelo’s servers. FreeloMCP only communicates with the Freelo API and does not store any data locally.
What transport protocols are supported?
Three transports are supported: Stdio (default for CLI tools), Streamable HTTP (recommended for HTTP clients), and SSE (deprecated). Use environment variables to configure the desired transport.
