OPEN-SOURCE MCP SERVER FOR FREEDCAMP

Run every Freedcamp project from Claude.

An open-source MCP server that connects Claude to Freedcamp: discover projects, create & update tasks, manage projects, and comment — in bulk, across every project.

View on GitHub Quick install
MIT licensed Node · TypeScript 12 tools
Freedcamp · your workspace
Launch Plan Marketing Mobile App
TaskStatusDue
Finalize Q3 roadmap Done Sep 20
Design landing hero In prog P
Write API docs To do Sep 26
Ask Claude: “add 3 tasks, assign the hero to Priya, due Friday” Run
12 tools · works across every project · stdio · HTTP · AWS SSM · MIT licensed
What it does

Built to run real Freedcamp work.

Hand Claude the keys to your workspace — discovery, tasks, projects and comments, all through one clean MCP server.

Every project, one server

Not pinned to a single project. Discover what you can access and act on any of them — a per-call project_id always wins, or set a default.

Tasks, projects & comments

The full lifecycle: create and update tasks, spin up and reshape projects (even archive or unarchive), and comment on tasks and other items.

Bulk by default, safe by design

Create or update many items in one call — even across projects. One bad item won't sink the batch, and listings are fully paginated with no silent truncation.

Your secrets stay yours

Credentials via environment variables or AWS SSM, so your config can reference parameter names — never the values. The optional HTTP transport can require a bearer token.

The toolbox

Twelve tools. Four jobs.

Everything an assistant needs to discover, build and run a Freedcamp workspace — sensible JSON in, structured results out, bulk by default.

Discovery

find the IDs to act on 3 tools

list_projects

Every project you can access — active and archived.

list_task_groups

The task lists in a project, with their list IDs.

list_users

Project members, with the user IDs for assignment.

Tasks

create, list, update, delete — in bulk 4 tools

add_task

Create one or many tasks — across projects in a single call.

update_task

Status, due date, assignee, list, priority — bulk edits too.

list_tasks

One project or all of them — fully paginated, no truncation.

delete_task

Permanently remove one or many tasks at once.

Projects

spin up & reshape projects 2 tools

add_project

Create projects — name, colour, group and view — in bulk.

update_project

Rename, recolour, regroup, archive or unarchive — required fields auto-filled.

Comments

talk on tasks & items 3 tools

add_comment

Comment on tasks and other items — HTML supported, in bulk.

update_comment

Edit the text of any existing comment.

delete_comment

Permanently remove one or many comments.

Up and running

Point Claude at your Freedcamp.

Installed from source: clone, build, and register with your API key + secret — or pull credentials from AWS SSM at startup.

bash — setup
# clone & build
$ git clone https://github.com/justadityaraj/freedcamp-mcp.git
$ cd freedcamp-mcp && npm install && npm run build

# register with Claude (credentials in env)
$ claude mcp add freedcamp -s user \
    -e FREEDCAMP_API_KEY=… -e FREEDCAMP_API_SECRET=… \
    -- node dist/server.js

# or keep secrets out of the config — pull them from AWS SSM
$ claude mcp add freedcamp -s user -e AWS_PROFILE=… -- node dist/ssm-launch.js

# ✓ Status: Connected — 12 tools ready
01

Grab your API key + secret: Freedcamp → avatar → Settings → API.

02

Optionally store them in AWS SSM and point at dist/ssm-launch.js.

03

Reload Claude — all 12 tools appear in your session.

Built to be used

Not a toy.

Live-tested against the Freedcamp API, with its awkward edges — mandatory edit fields, archive-only flags, due-date formats — handled so Claude doesn't have to.

12
tools shipped
4
tool categories
3
ways to run
38
offline tests
Who built this
Aditya Raj Singh
Aditya Raj Singh
builder · automation & MCP servers · homelab tinkerer

I wire Claude into the tools I run my work on. Freedcamp was one prompt away, so I built an MCP server that drives every project — tasks, projects and comments — and live-tested it on a real workspace. More of what I build over at adityarajsingh.com.

Questions

Freedcamp MCP, answered.

What is the Freedcamp MCP server?
It's an open-source Model Context Protocol (MCP) server that connects AI assistants like Claude to Freedcamp, with full read and write access across every project — so Claude can manage tasks, projects and comments directly inside your workspace.
What can AI do with Freedcamp through this MCP?
Twelve tools: discover projects, task lists and users; create, list, update and delete tasks; create and update projects (including archive / unarchive); and add, edit and delete comments. Everything supports bulk operations and works across all your projects.
Does it work across multiple Freedcamp projects?
Yes. A per-call project_id targets any project, or you can set a default. If neither is set, listing tools span every project you can access — and a single bulk call can even write to several projects at once.
How do I install the Freedcamp MCP with Claude Code?
It installs from source. Clone the repo, run npm install && npm run build, then claude mcp add freedcamp -s user -e FREEDCAMP_API_KEY=… -e FREEDCAMP_API_SECRET=… -- node dist/server.js. Both the env and AWS SSM paths are in the install section above.
Is the Freedcamp MCP server free and open source?
Yes — it's MIT-licensed and free to use, with the full source on GitHub.
Where do the Freedcamp credentials live?
You bring a Freedcamp API key + secret (Freedcamp → avatar → Settings → API). Pass them as environment variables, or store them in AWS SSM Parameter Store so your config references only the parameter names — never the secret values. The optional HTTP transport can also require a bearer token.

Hand your Freedcamp to Claude.

Open source, MIT licensed, every project in reach. Wire it into Claude Code today.

Star it on GitHub Read the docs