Freedcamp

You can manage Freedcamp tasks through a dedicated MCP server that supports both STDIO and HTTP transports. Use it to create, update, list, and delete tasks in a Freedcamp project, with bulk operation support and robust error handling. This guide walks you through using the server with MCP clients, installing it locally, and deploying it in containers or IDE integrations.

How to use

Choose your transport and connect your MCP client to the server to perform task operations in Freedcamp. The STDIO transport lets you run the server locally and connect through standard input/output, ideal for IDE integrations. The HTTP transport exposes a REST-like MCP endpoint for web apps, containers, and cloud deployments.

Key capabilities include creating multiple tasks at once with titles and optional fields like descriptions, priorities, due dates, and assignees; updating tasks including status changes; listing all tasks in a project; and permanently deleting tasks. You can perform these actions in bulk for efficiency.

To connect via STDIO, run the MCP client that launches the server with the STDIO configuration. To connect via HTTP, point your MCP client to the HTTP endpoint and use the same task operations over JSON requests.

Environment variables currently supported for credentials are FREEDCAMP_API_KEY, FREEDCAMP_API_SECRET, and FREEDCAMP_PROJECT_ID. These must be configured in your client or runner environment when starting the server.

STDIO transport interaction

In STDIO mode, you start the server by invoking the MCP runner in your project or IDE. The server runs locally and your MCP client communicates via STDIO.

{
  "type": "stdio",
  "name": "freedcamp",
  "command": "npx",
  "args": ["freedcamp-mcp"],
  "env": [
    {"name": "FREEDCAMP_API_KEY", "value": "your_api_key"},
    {"name": "FREEDCAMP_API_SECRET", "value": "your_api_secret"},
    {"name": "FREEDCAMP_PROJECT_ID", "value": "your_project_id"}
  ]
}

HTTP transport interaction

In HTTP mode, the MCP server exposes an endpoint suitable for web apps, containers, and cloud deployments. You connect your MCP client to the HTTP URL and perform the same task operations over HTTP.

{
  "type": "http",
  "name": "freedcamp_http",
  "url": "http://localhost:3000/mcp",
  "args": []
}

Running without a guide

If you plan to run the server directly, ensure you provide your Freedcamp credentials via environment variables and start the chosen transport. The HTTP endpoint runs on port 3000 by default, or a custom port can be set with PORT. The health endpoint is available at /health.

Test harness and verification

Use the provided test harnesses to verify all MCP functionalities for both transports. Start the HTTP server for HTTP tests, then run the tests to confirm server initialization, tool listing, single task operations, bulk operations, listing, and error handling.

# STDIO test (local)
npm test

# HTTP test (local)
npm run test:http

IDE integration

You can connect various MCP clients used in IDEs to this server. Use the STDIO configuration for local IDE integrations or the HTTP configuration for web-based tooling.

Docker and deployment notes

For production deployments, you can run the HTTP transport in a container. Start with the required environment variables and expose port 3000 for client connections. The HTTP transport is stateless and suitable for load-balanced setups.

Security considerations

Protect your Freedcamp API credentials. Do not commit credentials to version control. Use container secrets or a secure credential store in production environments.

Troubleshooting tips

If you encounter connection issues, verify that FREEDCAMP_API_KEY, FREEDCAMP_API_SECRET, and FREEDCAMP_PROJECT_ID are correct and that the target port is accessible. Check that the HTTP endpoint is reachable at the configured URL and that CORS settings allow your client.

Examples of common operations

Creating multiple tasks, updating several tasks, listing all tasks, and deleting tasks in bulk are all supported via the same MCP endpoints. Use bulk operations to streamline project work and ensure consistency across related updates.

Notes

The server provides environment-based credential handling and robust input validation to prevent invalid operations from reaching Freedcamp.

Available tools

freedcamp_add_task

Creates one or more new tasks in Freedcamp with parameters such as title, description, priority, due date, and assignee.

freedcamp_update_task

Updates one or more existing Freedcamp tasks, allowing changes to title, description, priority, due date, assignee, and status.

freedcamp_list_tasks

Retrieves all tasks for the configured Freedcamp project.

freedcamp_delete_task

Permanently deletes one or more tasks from Freedcamp by task ID.