mcp
mcpauth · remote officialcom.teamwork/mcp · v1.51.2
The Teamwork.com official MCP server helps teams efficiently manage client projects with AI.
run it
on your own machines, one way per deploy methodgenerated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
#!/usr/bin/env bash
# teamwork (com.teamwork/mcp), recipe docker (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-teamwork.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec docker run --rm --name mcp-my-agent-teamwork -p 127.0.0.1:${PORT}:8000 --env-file /etc/mcp/my-agent.env docker.io/teamwork/mcp:v1.51.2
[Unit]
Description=MCP server teamwork (toolset my-agent), generated by Hub
After=network-online.target docker.service
Wants=network-online.target
[Service]
Type=simple
User=mcp
Group=mcp
SupplementaryGroups=docker
EnvironmentFile=/etc/mcp/my-agent.env
Environment=HOME=/var/lib/mcp/teamwork
WorkingDirectory=/var/lib/mcp/teamwork
ExecStart=/opt/mcp/my-agent/bin/teamwork.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/teamwork
[Install]
WantedBy=multi-user.target
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
docker run --rm -p 127.0.0.1:8101:8000 -e TW_MCP_BEARER_TOKEN -e TW_MCP_LOG_FORMAT -e TW_MCP_LOG_LEVEL docker.io/teamwork/mcp:v1.51.2
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
# Generated by Hub for toolset "my-agent" (2026-10-17T22:01:21+00:00).
# Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
# cp .env.example .env # fill the ${VAR}s
# docker compose up -d && bash smoke.sh
# Remote servers are not here: clients reach them directly (see clients/).
name: mcp-my-agent
services:
teamwork:
image: docker.io/teamwork/mcp:v1.51.2
ports:
- 127.0.0.1:8101:8000
restart: unless-stopped
x-note: 'CHANGE_ME: check the image''s README for its transport and port; this assumes streamable
HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command
instead.'
environment:
TW_MCP_BEARER_TOKEN: ${TW_MCP_BEARER_TOKEN}
TW_MCP_LOG_FORMAT: ${TW_MCP_LOG_FORMAT}
TW_MCP_LOG_LEVEL: ${TW_MCP_LOG_LEVEL}
volumes:
npm-cache: {}
uv-cache: {}
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
# Generated by Hub for toolset "my-agent" (2026-10-17T22:01:21+00:00).
# kubectl create namespace mcp
# kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
# kubectl apply -f kubernetes.yaml
# Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
# with auth in front before exposing any of them.
apiVersion: v1
kind: Namespace
metadata:
name: mcp
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: teamwork
namespace: mcp
labels: &id001
app: teamwork
spec:
replicas: 1
selector:
matchLabels: *id001
template:
metadata:
labels: *id001
spec:
containers:
- name: teamwork
image: docker.io/teamwork/mcp:v1.51.2
ports:
- containerPort: 8000
name: http
env:
- name: TW_MCP_BEARER_TOKEN
valueFrom:
secretKeyRef:
name: mcp-credentials
key: TW_MCP_BEARER_TOKEN
- name: TW_MCP_LOG_FORMAT
valueFrom:
secretKeyRef:
name: mcp-credentials
key: TW_MCP_LOG_FORMAT
- name: TW_MCP_LOG_LEVEL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: TW_MCP_LOG_LEVEL
---
apiVersion: v1
kind: Service
metadata:
name: teamwork
namespace: mcp
spec:
selector:
app: teamwork
ports:
- port: 8000
targetPort: http
name: http
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
# Generated by Hub for toolset "my-agent" (2026-10-17T22:01:21+00:00).
# Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
# Each server under `servers` is one Deployment + Service; the keys after it configure
# upstream charts a worker verified.
servers:
teamwork:
enabled: true
replicas: 1
port: 8000
path: /mcp
container:
name: teamwork
image: docker.io/teamwork/mcp:v1.51.2
ports:
- containerPort: 8000
name: http
env:
- name: TW_MCP_BEARER_TOKEN
valueFrom:
secretKeyRef:
name: mcp-credentials
key: TW_MCP_BEARER_TOKEN
- name: TW_MCP_LOG_FORMAT
valueFrom:
secretKeyRef:
name: mcp-credentials
key: TW_MCP_LOG_FORMAT
- name: TW_MCP_LOG_LEVEL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: TW_MCP_LOG_LEVEL
# helm install my-agent helm/my-agent -n mcp
in the cloud
one click: the provider's deploy form opens filled in, in your own account- koyeb
-
The form opens with CHANGE_ME for each value you supply: TW_MCP_BEARER_TOKEN, TW_MCP_LOG_FORMAT, TW_MCP_LOG_LEVEL. Fill them in before you deploy.
Clients connect to the service's https://…koyeb.app address plus /mcp.
- azure
-
A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.
connect to it
copy what your client needshttps://mcp.ai.teamwork.com transport: streamable HTTP headers: Authorization
#!/usr/bin/env bash
# Asks every HTTP endpoint for its tool list over MCP streamable HTTP: first as MCP 2026-07-28
# (one request, no session), then, if the server does not answer that, as 2025-06-18
# (initialize, initialized, tools/list in the session).
set -uo pipefail
set -a; [ -f .env ] && source .env; set +a
post() { # url header version session body [curl options]
curl -sS -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \
${2:+-H "$2"} ${3:+-H "MCP-Protocol-Version: $3"} ${4:+-H "Mcp-Session-Id: $4"} "${@:6}" -d "$5" "$1"
}
probe() { # name url [header]
local name="$1" url="$2" hdr="${3:-}" out sid
local meta='{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientCapabilities":{},"io.modelcontextprotocol/clientInfo":{"name":"smoke","version":"0"}}'
out=$(post "$url" "$hdr" 2026-07-28 "" '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{"_meta":'"$meta"'}}' -H "Mcp-Method: tools/list")
if ! grep -q '"result"' <<<"$out"; then
local init='{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"smoke","version":"0"}}}'
sid=$(post "$url" "$hdr" "" "" "$init" -D - -o /dev/null | awk 'tolower($1)=="mcp-session-id:"{print $2}' | tr -d "\r")
post "$url" "$hdr" 2025-06-18 "$sid" '{"jsonrpc":"2.0","method":"notifications/initialized"}' -o /dev/null
out=$(post "$url" "$hdr" 2025-06-18 "$sid" '{"jsonrpc":"2.0","id":2,"method":"tools/list"}')
fi
# tool names only: a 2026-07-28 answer names the server in _meta too
sed 's/"io\.modelcontextprotocol\/serverInfo": *{[^}]*}//g' <<<"$out" | grep -o '"name": *"[^"]*"' \
| head -20 | sed "s/^/ $name: /" || echo " $name: no answer"
}
probe teamwork https://mcp.ai.teamwork.com "Authorization: ${TEAMWORK_AUTHORIZATION}"
{
"mcpServers": {
"teamwork": {
"url": "https://mcp.ai.teamwork.com",
"headers": {
"Authorization": "${TEAMWORK_AUTHORIZATION}"
}
}
}
}
#!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add --transport http teamwork https://mcp.ai.teamwork.com --header "Authorization: ${TEAMWORK_AUTHORIZATION}"
{
"mcpServers": {
"teamwork": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.ai.teamwork.com",
"--header",
"Authorization:${TEAMWORK_AUTHORIZATION}"
]
}
}
}
{
"servers": {
"teamwork": {
"type": "http",
"url": "https://mcp.ai.teamwork.com",
"headers": {
"Authorization": "${TEAMWORK_AUTHORIZATION}"
}
}
}
}
name: my-agent target: local servers: - hub: com.teamwork/mcp
- not probed yet: tools unpinned, ingest lists them
tools
Probe result: needs authremote: HTTP 401: MCPError: Server returned an error response
runs · 1
the latest tests of this entry by the hub and its workers, newest first| date | worker | method | status | sandbox | reason |
|---|---|---|---|---|---|
| 2026-10-16 09:08 | local-mac | remote | needs auth | none | remote: HTTP 401: MCPError: Server returned an error response |