MCP.so
Sign In

Teamwork MCP

@Vizioz

About Teamwork MCP

MCP server to connect to the Teamwork API

Basic information

Category

Other

License

MIT

Runtime

node

Transports

stdio

Publisher

Vizioz

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "teamwork-mcp-vizioz": {
      "command": "npx",
      "args": [
        "@vizioz/teamwork-mcp"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Teamwork MCP?

An MCP server that connects to the Teamwork API, providing a simplified interface for interacting with Teamwork projects and tasks. It is designed for developers using MCP-compatible clients like Cursor, Claude Desktop, or Windsurf.

How to use Teamwork MCP?

Install and run via npx: npx @vizioz/teamwork-mcp. Provide Teamwork credentials through environment variables (TEAMWORK_DOMAIN, TEAMWORK_USERNAME, TEAMWORK_PASSWORD), a .env file, or command-line arguments (--domain, --user, --pass). Optionally filter available tools using --allow-tools or --deny-tools with individual tool names or groups (Projects, Tasks, People, etc.). Logging can be disabled with --disable-logging.

Features of Teamwork MCP

  • Connect to Teamwork API and manage projects.
  • Full CRUD for tasks, subtasks, and comments.
  • Retrieve and manage companies and people.
  • Reporting for task completion and utilization.
  • Time entries and project allocations.
  • Tool filtering and configurable logging.

Use cases of Teamwork MCP

  • Track project tasks and subtasks in Teamwork.
  • Get metrics on completed and late tasks.
  • Manage people assignments and utilization.
  • Create companies and update person information.
  • Generate user task completion and utilization reports.

FAQ from Teamwork MCP

How do I provide Teamwork credentials?

Through environment variables (TEAMWORK_DOMAIN, TEAMWORK_USERNAME, TEAMWORK_PASSWORD), a .env file, or command-line arguments (--domain, --user, --pass).

Can I limit which tools are available?

Yes, use --allow-tools or --deny-tools with individual tool names or groups (Projects, Tasks, People, Reporting, Time, Comments). If both are provided, the allow list takes precedence.

How do I disable logging?

Use the --disable-logging or --no-logging command-line argument, or set the DISABLE_LOGGING=true environment variable.

What clients are supported?

The server integrates with Cursor, Claude Desktop, and Windsurf via MCP configuration using stdio transport.

What are the runtime requirements

Comments

More Other MCP servers