Freedcamp MCP

Freedcamp MCP now has a permanent address: https://mcp.freedcamp.com/mcp. Point any MCP client at it, sign in once in your browser, and your AI assistant can read and change things in your Freedcamp account without you tabbing over.

The first version went up in May. It did the job, but you had to hand your API key and secret to your client, which sent them along with every request. And none of it lived on freedcamp.com yet.

Both of those are fixed, the tool list grew, and there’s a real docs site at mcp.freedcamp.support.

What’s New in Freedcamp MCP?

MCP is the protocol AI clients use to call tools. Freedcamp MCP is a hosted server that speaks it. Claude, Cursor, Codex CLI, and the rest can work inside your projects directly, instead of you copying things back and forth.

Three things changed since May. The address is on freedcamp.com, and you sign in with OAuth instead of keeping keys in a config file. The catalog grew from the 80-plus tools we started with to 102.

That covers tasks, lists, milestones, time tracking, the Issue Tracker, discussions, wikis, files, the calendar, CRM, comments, notifications, custom fields, and your account.

How It Works

Step 1 API Key: In Freedcamp, go to Settings → API and create a key. You get a key and a secret. The secret is shown once, so copy it now.

Step 2 Add the Connector: In Claude Desktop, open Settings → Connectors and choose Add → Add custom connector. Freedcamp MCP isn’t in the browse list; it’s your own hosted endpoint. Give it a name (it’s only the label you’ll see in the list), paste the endpoint, and click Continue.

Claude probes the server and pre-selects the right options, both marked Detected. Leave them alone, skip the headers, and click Add.

Other clients take one line. Claude Code:

claude mcp add --transport http freedcamp https://mcp.freedcamp.com/mcp

Then run /mcp in a session and pick Authenticate. Cursor, Codex CLI, Cline, Continue, and VS Code each take a short config block: the URL and, for some, a transport type, but never a key. The exact block for each is in the docs, or let install-mcp write it for you:

npx install-mcp https://mcp.freedcamp.com/mcp --client claude --oauth yes

Step 3 Authorize: A browser page opens. Paste the key and secret from Step 1 and press Authorize. Your credentials go to Freedcamp, never to the AI client.

A bad key fails right there, not on your first request. A good one gets your client a token that lasts 30 days. After that, you authorize again the same way.

Step 4 Ask: Say “list my Freedcamp projects” to confirm the connection. Then ask for something real:

• “Turn these meeting notes into tasks in the Task Vault project, due next Friday, assigned to me.”
• “Mark every task in the Release 4.1 list completed and move the leftovers to Release 4.2.”
• “Log 45 minutes on the Acme refactor for today and mark it billed.”
• “Summarize my unread notifications and tell me which ones need something from me.”

Name projects and lists the way they appear in Freedcamp, case included, because names are matched exactly. And every delete is marked destructive, so your client can ask before it runs one. Leave those confirmations on.

Benefits of Freedcamp MCP

• One address on freedcamp.com, nothing to install, no server to run
• Sign in once with OAuth. Your key and secret never sit in a config file
• 102 tools, up from the 80-plus in May
• Helper tools resolve your groups, projects, and apps by name, so the assistant stops guessing at IDs
• Batch-edit up to 500 tasks in one request
• Every tool is marked read-only, writes, or destructive, so your client can ask before a delete
• No false successes. Starting a timer that’s already running comes back as an error instead of a fake success
• Your whole team can point at the same address. Everyone signs in with their own key, and nobody sees anyone else’s workspace
• It can only do what you can do. There’s no separate quota; the usual API limits and your plan’s permissions apply
• Docs at mcp.freedcamp.support, with the config for each client it supports, eight prompt recipes, and an FAQ

Let Us Know Your Thoughts

The tool list is the part we want to hear about. If there’s something you do in Freedcamp that your assistant can’t reach yet, tell us the app and what you tried. Same if your client speaks MCP and the docs don’t cover it.

And if you need a self-hosted or local version, say so on the GitHub repository. The hosted endpoint is the only one we support right now, and the repo is where to ask.

Get Started Today!

Create an API key, add the connector, and ask your assistant to list your projects. Then ask it to do the thing you’d normally tab over for. Set it up at mcp.freedcamp.support →