Teamcamp MCP server
12 operations0 webhooks
Project management for client work. Read and create projects, their task groups and their tasks, with the workspace members and customers a project is built from.
Try Teamcamp with your agent
Connect Teamcamp, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in Teamcamp on my account, then run one read-only example and show me the result.
Teamcamp tools and triggers
Tools are what your agent can do in Teamcamp through Corsair's MCP server. Triggers are the Teamcamp events a routine can start from.
Projects
- CreateWrite
Create a project, optionally from a template and with a customer and dates
projects.create
- DeleteDestructive
Delete a project. It is archived rather than erased: it leaves the project list, but a read by id still returns it marked archived
projects.delete
- GetRead-only
Read one project: its members, owner, dates and workflow statuses, which a task create needs for its status id
projects.get
- ListRead-only
List the projects in the workspace, by id and name
projects.list
- UpdateWrite
Change a project name, description, dates or customer
projects.update
Tasks
- CreateWrite
Create a task in a project, with a priority, due date, assignees, group, status, milestone, estimate and attachments
tasks.create
- GetRead-only
Read one task, with its assignees, labels, files and comments
tasks.get
- ListRead-only
List the tasks of a project, optionally only the completed or only the open ones
tasks.list
Account
- VerifyRead-only
Read the workspace the key belongs to, which also confirms the key is valid
account.verify
Customers
- ListRead-only
List the customers a project can be billed to, with their clients
customers.list
Groups
- ListRead-only
List the task groups of a project, by id and name
groups.list
Users
- ListRead-only
List the workspace members, with their role, timezone and last seen time
users.list
Connect Teamcamp to Claude, ChatGPT or Cursor
- 1
Connect Teamcamp in Corsair
Add your Teamcamp API key once in Corsair. Corsair stores the credential encrypted and makes the Teamcamp API calls for your agent, so it never goes into a prompt or a config file. Connect Teamcamp
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Teamcamp. On a ChatGPT personal plan, connect Teamcamp here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Teamcamp's read and write operations run right away and its 1 destructive operation waits for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/teamcamp, add the Teamcamp plugin, and connect with an API key. Then call methods like corsair.teamcamp.api.account.verify() from your app. Corsair keeps each tenant isolated.
Yes. Teamcamp requires an API key from your Teamcamp account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Teamcamp, GitHub, Notion, Stripe, and the rest. Trigger Teamcamp from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for project management for client work. Read and create projects, their task groups and their tasks, with the workspace members and customers a project is built from. Common builds include sync jobs, admin tooling, and agents that call Teamcamp APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Teamcamp API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/teamcamp in the open repo. When Teamcamp ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Teamcamp data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Teamcamp data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put Teamcamp on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 1 destructive Teamcamp operation. You can change a link's mode at hub.corsair.dev/me.