Freelo

This Freelo MCP Server provides a set of tools that connect to the Freelo project management API, letting you read task details, list subtasks, and download files attached to task comments. It runs as a Model Context Protocol (MCP) server that you can integrate into Claude Code or Claude Desktop to interact with Freelo from your conversations and workflows.

How to use

You leverage the Freelo MCP Server through an MCP client setup. Start by configuring your MCP server in your Claude environment, then invoke the available tools to get task details, list subtasks, or download files. The server exposes three tools you can call in your conversations: freelo_get_task, freelo_list_task_subtasks, and freelo_download_file. Each tool returns structured Freelo data you can inspect and use in your prompts.

Typical usage patterns include retrieving a task along with its comments and attachments, reviewing subtasks and their progress, and downloading a file attachment by its UUID. After configuring credentials, you can issue natural language requests like, “Get details for Freelo task 12345,” or “Download the file with UUID 550e8400-….”.

How to install

Prerequisites: you need Node.js and npm installed on your system. You also need access to your Freelo API key (email and API key). Take note of your Freelo API key from your Freelo dashboard.

Step 1. Install dependencies and build the project when you clone or obtain the Freelo MCP server code.

# Install dependencies
npm install

# Build the project
npm run build

# Optional: watch mode during development
npm run watch

Additional setup and configuration

Configure your Freelo MCP server in Claude Code or Claude Desktop to supply your Freelo credentials. You will set your Freelo email and API key as environment variables when starting the MCP server.

Configuration for running via Claude Code (manual) shows the MCP server entry with the command to execute and environment variables.

{
  "mcpServers": {
    "freelo-mcp": {
      "command": "npx",
      "args": ["-y", "@liquiddesign/freelo-mcp"],
      "env": {
        "FREELO_EMAIL": "your-email@example.com",
        "FREELO_API_KEY": "your-api-key-here"
      }
    }
  }
}

Development and local running notes

For local development, you may build the project and run it directly with Node, pointing to the built entry file.

Example start command from development notes uses a full path to the built index file.

{
  "mcpServers": {
    "freelo-mcp": {
      "command": "node",
      "args": ["/absolute/path/to/freelo-mcp/dist/index.js"],
      "env": {
        "FREELO_EMAIL": "your-email@example.com",
        "FREELO_API_KEY": "your-api-key-here"
      }
    }
  }
}

Notes on security and maintenance

Keep your Freelo API key secure. Do not commit credentials to public repositories. Use environment variables to inject credentials at runtime, and rotate keys regularly as part of your security practices.

If you update tools or the MCP server, rebuild and restart the MCP server so changes are loaded by your Claude client.

Available tools

freelo_get_task

Retrieve detailed information about a Freelo task, including comments and attached files.

freelo_list_task_subtasks

List all subtasks for a given task along with their completion status and related metadata.

freelo_download_file

Download a file from a task comment using its UUID and return the file path and metadata.