Skip to content

Add Teamwork MCP server to registry #51

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

BrandonABarringer
Copy link

  • Add server configuration for Vizioz/Teamwork-MCP
  • Supports project management, task creation, and subtasks
  • Category: project-management
  • Required env vars: TEAMWORK_DOMAIN, TEAMWORK_USERNAME, TEAMWORK_PASSWORD

- Add server configuration for Vizioz/Teamwork-MCP
- Supports project management, task creation, and subtasks
- Category: project-management
- Required env vars: TEAMWORK_DOMAIN, TEAMWORK_USERNAME, TEAMWORK_PASSWORD

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
@BrandonABarringer BrandonABarringer requested a review from a team as a code owner July 6, 2025 17:47
@ipedrazas
Copy link
Contributor

It seems that the Server cannot list the tools without a valid connection:


task build -- --tools teamwork
task: [build] go run ./cmd/build --tools teamwork
[+] Building 182.4s (11/11) FINISHED                                                                                                                                                                                                       docker:desktop-linux
 => [internal] load git source https://github.com/Vizioz/Teamwork-MCP.git#main                                                                                                                                                                             1.0s
 => [internal] load metadata for docker.io/library/debian:bullseye-slim                                                                                                                                                                                    1.2s
 => [auth] library/debian:pull token for registry-1.docker.io                                                                                                                                                                                              0.0s
 => [1/7] FROM docker.io/library/debian:bullseye-slim@sha256:b5f9bc44bdfbd9d551dfdd432607cbc6bb5d9d6dea726a1191797d7749166973                                                                                                                              5.0s
 => => resolve docker.io/library/debian:bullseye-slim@sha256:b5f9bc44bdfbd9d551dfdd432607cbc6bb5d9d6dea726a1191797d7749166973                                                                                                                              0.1s
 => => sha256:00ce3d02ade4a2c8e5e37b1a218bb5c24c995bd8757095b89316c42854286fe8 28.74MB / 28.74MB                                                                                                                                                           4.3s
 => => extracting sha256:00ce3d02ade4a2c8e5e37b1a218bb5c24c995bd8757095b89316c42854286fe8                                                                                                                                                                  0.5s
 => [2/7] RUN groupadd -r service-user &&     useradd -u 1987 -r -m -g service-user service-user &&     mkdir -p /home/service-user/.local/bin /app /home/service-user/.npm-global &&     chown -R service-user:service-user /home/service-user /app       0.7s
 => [3/7] RUN apt-get update &&     apt-get install -y --no-install-recommends curl &&     curl -fsSL https://deb.nodesource.com/setup_22.x | bash - &&     apt-get update &&     apt-get install -y nodejs npm &&     node --version &&     npm --vers  149.0s
 => [4/7] WORKDIR /home/service-user                                                                                                                                                                                                                       0.3s
 => [5/7] RUN npm config set prefix '/home/service-user/.npm-global'                                                                                                                                                                                       0.5s
 => [6/7] RUN npm install -g [email protected]                                                                                                                                                                                                              2.8s
 => [7/7] WORKDIR /app                                                                                                                                                                                                                                     0.2s
 => exporting to image                                                                                                                                                                                                                                    21.1s
 => => exporting layers                                                                                                                                                                                                                                   16.9s
 => => exporting manifest sha256:078effced981f9fec4315c0806add9e67d7c644958a6b13013cf8cfdaab27a77                                                                                                                                                          0.1s
 => => exporting config sha256:317900f7c260e342e1cbe6d23027eeab4f717206fd5ab8fe7feb58c8541b35af                                                                                                                                                            0.1s
 => => exporting attestation manifest sha256:ec0612ff8c6621d5e4f6ee0eae8bdf3fac2c358e3120127f47a3040609dd49c3                                                                                                                                              0.1s
 => => exporting manifest list sha256:1a8420f81b9d30bd71ff3adb70756f052203d9548eb32831e57deb39f736011c                                                                                                                                                     0.1s
 => => naming to docker.io/library/check:latest                                                                                                                                                                                                            0.0s
 => => unpacking to docker.io/library/check:latest                                                                                                                                                                                                         3.8s
 => => naming to docker.io/mcp/teamwork:latest                                                                                                                                                                                                             0.0s
 => => unpacking to docker.io/mcp/teamwork:latest                                                                                                                                                                                                          0.0s

What's next:
    View a summary of image vulnerabilities and recommendations → docker scout quickview
2025/07/08 11:01:31 initializing mcp/teamwork: file:///home/service-user/.npm-global/lib/node_modules/mcp-proxy/dist/bin/mcp-proxy.js:46
        this.serverParams.args ?? [],
                                ^

SyntaxError: Unexpected token '?'
    at Loader.moduleStrategy (internal/modules/esm/translators.js:133:18)
    at async link (internal/modules/esm/module_job.js:42:21)
exit status 1
task: Failed to run task "build": exit status 1

To build Docker images for the mcp namespace, we need to be able to list the available tools.

@BrandonABarringer
Copy link
Author

Ah. I was hoping that would be fixed before your review. I opened a ticket a couple days ago and it should be fixed soon Vizioz/Teamwork-MCP#8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants