Can I use Teamwork as a CLI?

Yes. KosmoKrator exposes a Teamwork CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Teamwork through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Teamwork tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Teamwork credentials stored?

Teamwork credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Teamwork MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Teamwork MCP Integration for LangChain

Connect Teamwork to LangChain through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write API token auth

Submit Teamwork feedback View package source

Connect Teamwork to LangChain

Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls.

Use the MCP gateway when the agent should discover tools, or wrap kosmo integrations:call for fixed chains. The gateway is local, scoped to this integration, and starts with --write=deny so LangChain can inspect read-capable tools without receiving write access by default.

Teamwork MCP Config for LangChain

Keep the gateway scoped to the integration and operation class needed by the chain.

{
  "mcpServers": {
    "kosmokrator-teamwork": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=teamwork",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=teamwork --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Teamwork instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Teamwork Tools Visible to LangChain

LangChain sees stable MCP tool names generated from the Teamwork integration catalog.

MCP tool	Source function	Type	Description
`integration__teamwork__teamwork_create_task`	`teamwork.teamwork_create_task`	Write	Create a new task in Teamwork.
`integration__teamwork__teamwork_get_current_user`	`teamwork.teamwork_get_current_user`	Read	Get the currently authenticated Teamwork user.
`integration__teamwork__teamwork_get_project`	`teamwork.teamwork_get_project`	Read	Get detailed information about a Teamwork project.
`integration__teamwork__teamwork_get_task`	`teamwork.teamwork_get_task`	Read	Get detailed information about a Teamwork task.
`integration__teamwork__teamwork_list_projects`	`teamwork.teamwork_list_projects`	Read	List projects in Teamwork with optional filters.
`integration__teamwork__teamwork_list_tasks`	`teamwork.teamwork_list_tasks`	Read	List tasks in Teamwork with optional filters.
`integration__teamwork__teamwork_list_timers`	`teamwork.teamwork_list_timers`	Read	List time timers for the authenticated user in Teamwork.

Related Teamwork Pages

Teamwork CLIUse direct JSON commands instead of MCP discovery. Teamwork MCPFull gateway reference and MCP tool names. KosmoKrator for LangChainClient-level gateway setup.