Comunio
mcpotherio.github.josetorronteras/comunio · v1.0.2
Read and operate a Comunio fantasy football team: squad, market, offers, lineup
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
# comunio (io.github.josetorronteras/comunio), recipe docker (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-comunio.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec docker run --rm --name mcp-my-agent-comunio -p 127.0.0.1:${PORT}:8000 --env-file /etc/mcp/my-agent.env ghcr.io/josetorronteras/comunio-mcp:1.0.2
[Unit]
Description=MCP server comunio (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/comunio
WorkingDirectory=/var/lib/mcp/comunio
ExecStart=/opt/mcp/my-agent/bin/comunio.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/comunio
[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 COMUNIO_USERNAME -e COMUNIO_PASSWORD -e COMUNIO_TIMEZONE -e COMUNIO_USER_AGENT ghcr.io/josetorronteras/comunio-mcp:1.0.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-18T08:27:07+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:
comunio:
image: ghcr.io/josetorronteras/comunio-mcp:1.0.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:
COMUNIO_USERNAME: ${COMUNIO_USERNAME}
COMUNIO_PASSWORD: ${COMUNIO_PASSWORD}
COMUNIO_TIMEZONE: ${COMUNIO_TIMEZONE}
COMUNIO_USER_AGENT: ${COMUNIO_USER_AGENT}
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-18T08:27:07+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: comunio
namespace: mcp
labels: &id001
app: comunio
spec:
replicas: 1
selector:
matchLabels: *id001
template:
metadata:
labels: *id001
spec:
containers:
- name: comunio
image: ghcr.io/josetorronteras/comunio-mcp:1.0.2
ports:
- containerPort: 8000
name: http
env:
- name: COMUNIO_USERNAME
valueFrom:
secretKeyRef:
name: mcp-credentials
key: COMUNIO_USERNAME
- name: COMUNIO_PASSWORD
valueFrom:
secretKeyRef:
name: mcp-credentials
key: COMUNIO_PASSWORD
- name: COMUNIO_TIMEZONE
valueFrom:
secretKeyRef:
name: mcp-credentials
key: COMUNIO_TIMEZONE
- name: COMUNIO_USER_AGENT
valueFrom:
secretKeyRef:
name: mcp-credentials
key: COMUNIO_USER_AGENT
---
apiVersion: v1
kind: Service
metadata:
name: comunio
namespace: mcp
spec:
selector:
app: comunio
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-18T08:27:07+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:
comunio:
enabled: true
replicas: 1
port: 8000
path: /mcp
container:
name: comunio
image: ghcr.io/josetorronteras/comunio-mcp:1.0.2
ports:
- containerPort: 8000
name: http
env:
- name: COMUNIO_USERNAME
valueFrom:
secretKeyRef:
name: mcp-credentials
key: COMUNIO_USERNAME
- name: COMUNIO_PASSWORD
valueFrom:
secretKeyRef:
name: mcp-credentials
key: COMUNIO_PASSWORD
- name: COMUNIO_TIMEZONE
valueFrom:
secretKeyRef:
name: mcp-credentials
key: COMUNIO_TIMEZONE
- name: COMUNIO_USER_AGENT
valueFrom:
secretKeyRef:
name: mcp-credentials
key: COMUNIO_USER_AGENT
# 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: COMUNIO_USERNAME, COMUNIO_PASSWORD, COMUNIO_TIMEZONE, COMUNIO_USER_AGENT. 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 needsdocker run -i --rm -e COMUNIO_USERNAME -e COMUNIO_PASSWORD -e COMUNIO_TIMEZONE -e COMUNIO_USER_AGENT ghcr.io/josetorronteras/comunio-mcp:1.0.2
{
"mcpServers": {
"comunio": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"COMUNIO_USERNAME",
"-e",
"COMUNIO_PASSWORD",
"-e",
"COMUNIO_TIMEZONE",
"-e",
"COMUNIO_USER_AGENT",
"ghcr.io/josetorronteras/comunio-mcp:1.0.2"
],
"env": {
"COMUNIO_USERNAME": "${COMUNIO_USERNAME}",
"COMUNIO_PASSWORD": "${COMUNIO_PASSWORD}",
"COMUNIO_TIMEZONE": "${COMUNIO_TIMEZONE}",
"COMUNIO_USER_AGENT": "${COMUNIO_USER_AGENT}"
}
}
}
}
#!/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 comunio -e "COMUNIO_USERNAME=${COMUNIO_USERNAME}" -e "COMUNIO_PASSWORD=${COMUNIO_PASSWORD}" -e "COMUNIO_TIMEZONE=${COMUNIO_TIMEZONE}" -e "COMUNIO_USER_AGENT=${COMUNIO_USER_AGENT}" -- docker run -i --rm -e COMUNIO_USERNAME -e COMUNIO_PASSWORD -e COMUNIO_TIMEZONE -e COMUNIO_USER_AGENT ghcr.io/josetorronteras/comunio-mcp:1.0.2
{
"mcpServers": {
"comunio": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"COMUNIO_USERNAME",
"-e",
"COMUNIO_PASSWORD",
"-e",
"COMUNIO_TIMEZONE",
"-e",
"COMUNIO_USER_AGENT",
"ghcr.io/josetorronteras/comunio-mcp:1.0.2"
],
"env": {
"COMUNIO_USERNAME": "${COMUNIO_USERNAME}",
"COMUNIO_PASSWORD": "${COMUNIO_PASSWORD}",
"COMUNIO_TIMEZONE": "${COMUNIO_TIMEZONE}",
"COMUNIO_USER_AGENT": "${COMUNIO_USER_AGENT}"
}
}
}
}
{
"servers": {
"comunio": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"COMUNIO_USERNAME",
"-e",
"COMUNIO_PASSWORD",
"-e",
"COMUNIO_TIMEZONE",
"-e",
"COMUNIO_USER_AGENT",
"ghcr.io/josetorronteras/comunio-mcp:1.0.2"
],
"env": {
"COMUNIO_USERNAME": "${COMUNIO_USERNAME}",
"COMUNIO_PASSWORD": "${COMUNIO_PASSWORD}",
"COMUNIO_TIMEZONE": "${COMUNIO_TIMEZONE}",
"COMUNIO_USER_AGENT": "${COMUNIO_USER_AGENT}"
}
}
}
}
name: my-agent target: local servers: - hub: io.github.josetorronteras/comunio
- not probed yet: tools unpinned, ingest lists them
tools
Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.