How to connect Teamcamp to OpenClaw
Connect Teamcamp to OpenClaw with ClawLink: paste your Teamcamp key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine.
TeamcampAPI KEYMCPAn all-in-one project management tool designed for teams to efficiently manage projects, collaborate seamlessly, and streamline workflows.. Once connected, OpenClaw can read and act on Teamcamp from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Teamcamp access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Teamcamp setup: install one ClawHub skill, connect Teamcamp in the browser, and OpenClaw can call real Teamcamp actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Teamcamp.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Teamcamp
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Teamcamp?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Teamcamp in the ClawLink dashboard — paste your Teamcamp API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Teamcamp, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Teamcamp is connected in the dashboard, that agent calls the same 14 Teamcamp tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Teamcamp MCP for OpenClaw
Looking for a Teamcamp MCP server for OpenClaw? ClawLink connects Teamcamp to OpenClaw and exposes 14 Teamcamp tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Teamcamp integration works the same way.
What the OpenClaw Teamcamp integration can do
14 Teamcamp tools are ready for OpenClaw once the account is connected. The 13 below are the ones people reach for most; your agent can call all 14.
13 of 14 Teamcamp tools for OpenClaw
| Tool | What it does |
|---|---|
Get company customers teamcamp_get_company_customers | Retrieve all customers in the company/workspace |
Get company users teamcamp_get_company_users | Retrieve all users in the company/workspace |
Get project details teamcamp_get_project_details | Get comprehensive project details including core fields, configuration, user data, feature |
Get project groups teamcamp_get_project_groups | Retrieve all groups within a specific project |
Get project list teamcamp_get_project_list | Retrieve all projects within the workspace |
Get task teamcamp_get_task | Retrieve details of a specific task by its unique identifier |
Get task list filtered teamcamp_get_task_list_filtered | Retrieve a list of tasks from a project with optional completion status filtering |
Create project teamcamp_create_project | Create a new project in the workspace |
Create task teamcamp_create_task | Create a new task within a specified project |
Create task2 teamcamp_create_task2 | Create a new task in a TeamCamp project |
Post task comment teamcamp_post_task_comment | Post a new comment on a task |
Update project teamcamp_update_project | Update an existing project's details by its unique identifier |
Update task teamcamp_update_task | Update an existing task by its unique identifier |
Try it: find the Teamcamp tool you need
Browse the 13 Teamcamp tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Teamcamp, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Teamcamp, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Teamcamp, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Teamcamp, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Teamcamp working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Teamcamp API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Teamcamp account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Teamcamp. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Teamcamp actions to the runtime in a format your agent can reliably use. | 14 tools for Teamcamp are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Teamcamp to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Teamcamp in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Teamcamp key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Teamcamp skill but can't call the tools
The ClawHub skill teaches OpenClaw about Teamcamp, but the calls run through the ClawLink plugin and your connected account. Make sure Teamcamp is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Teamcamp from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Teamcamp tools
Teamcamp tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Teamcamp call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Teamcamp returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Teamcamp has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Teamcamp integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Teamcamp: link your Teamcamp account once in the browser and OpenClaw can call the Teamcamp API through 14 ready-made tools — no custom code or token handling.
How do I add Teamcamp to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Teamcamp skill from ClawHub, then you click Connect in the dashboard to authorize Teamcamp. OpenClaw calls the tools from the next message — no config files, and the Teamcamp key you paste is stored server-side instead of in your environment.
How long does it take to connect Teamcamp to OpenClaw?
About two minutes. Sign in, click Connect next to Teamcamp in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Teamcamp up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Teamcamp working from chat.
OpenClaw installed the Teamcamp skill but can't call the tools
The ClawHub skill teaches OpenClaw about Teamcamp, but the calls run through the ClawLink plugin and your connected account. Make sure Teamcamp is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
