Freelo MCP Server (Neoficiální) > Upozornění: Toto je neoficiální komunitní projekt a není přímo podporován společností Freelo. . The freelomcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

MCP Server pro Freelo API v1 - kompletní implementace Model Context Protocol serveru pro komunikaci s Freelo API. Freelo je česká služba pro projektové řízení a správu úkolů.

Its toolset

Everything the assistant can do here goes through one of these:

• get_projects — Získání vlastních aktivních projektů
• get_all_projects — Všechny projekty (vlastní i sdílené) s pagination
• get_project_details — Detail projektu včetně workers a tasklists
• get_invited_projects — Projekty, kam jsem byl pozván
• get_archived_projects — Archivované projekty
• get_template_projects — Šablonové projekty s filtry
• get_user_projects — Projekty konkrétního uživatele
• get_project_workers — Seznam pracovníků na projektu
• get_project_manager_of — Projekty kde jsem PM
• get_project_tasklists — Všechny tasklisty v projektu
• create_project — Vytvoření nového projektu
• create_project_from_template — Vytvoření z šablony

Configuration

You will need 3 environment variables: FREELO_EMAIL, FREELO_API_KEY, FREELO_USER_AGENT. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. FreeloMCP's toolset — get_projects, get_all_projects, get_project_details and 11 more — is a fair guide to whether it matches your workflow. It is maintained by karlost; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch FreeloMCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the freelomcp mcp server does with a few real requests.