Skip to content

t1k:comms-mcp:setup

FieldValue
Modulecore
Version0.7.9
Effortlow
Tools—
/t1k:comms-mcp:setup

Overview + registration entrypoint for the comms-mcp wrapper kit.

Team-communication MCP servers for four chat platforms, plus Google Workspace. The kit ships no server source: Discord uses the hosted discord-mcp server (no local install); each other platform uses a The1Studio fork (Google Workspace: a private installer repo), set up from a clone by its setup script. Stdio transport, except Google Workspace (a loopback HTTP service on 127.0.0.1:9103; see its skill) and the hosted Discord server.

Setting up a comms server, or routing a “send / post / notify” request. For a specific platform, the matching t1k-comms-mcp-<platform> skill carries the details; for destination routing invoke the t1k-comms-mcp-core-router agent by name: deliberately, this kit is routing-free (it ships no t1k-routing-*.json fragment and the router declares roles: none), so the router is reached through this skill, not through role or keyword discovery. That is by design, not a gap (see the router agent’s “How you are reached” section).

This skill stays on the reasoning tier. Its scripts/install-*.sh clone a fork, run bun install/build, and claude mcp add a server with the user’s credentials: they mutate the local machine and register credentialed servers, so a person or reasoning-tier agent runs them after confirming platform and credentials. No cheap-tier agent is delegated any step (routing SSOT: rules/orchestration-rules.md § “Task-Type → Agent Routing”).

PlatformSkillFork (source)Setup
Discordt1k-comms-mcp-discordThe1Studio/discord-mcp (hosted)none: no install; use mcp__discord-mcp__*
Slackt1k-comms-mcp-slackThe1Studio/slack-mcp-server~/.claude/skills/t1k-comms-mcp-setup/scripts/install-slack.sh
Lark / Feishut1k-comms-mcp-larkThe1Studio/lark-openapi-mcp~/.claude/skills/t1k-comms-mcp-setup/scripts/install-lark.sh
WhatsAppt1k-comms-mcp-whatsappThe1Studio/whatsapp-mcp~/.claude/skills/t1k-comms-mcp-setup/scripts/install-whatsapp.sh
Google Workspacet1k-comms-mcp-google-workspaceThe1Studio/google-workspace-mcp (private, pinned tag)~/.claude/skills/t1k-comms-mcp-setup/scripts/install-google-workspace.sh --client-json PATH

(For a project-scoped install the scripts live at .claude/skills/t1k-comms-mcp-setup/scripts/install-<platform>.sh instead of ~/.claude/skills/t1k-comms-mcp-setup/scripts/….)

  1. (Not for Discord, which is hosted.) Run ~/.claude/skills/t1k-comms-mcp-setup/scripts/install-<platform>.sh (for a project-scoped install: .claude/skills/t1k-comms-mcp-setup/scripts/install-<platform>.sh): clones the fork, builds its entrypoint, and (if the platform’s token env vars are set) registers it via claude mcp add --scope user, else prints the exact command to run yourself. Install dir is ${T1K_COMMS_DIR:-$HOME/.theonekit-comms}/<platform>; scripts are idempotent. To install everything at once, run ~/.claude/skills/t1k-comms-mcp-setup/scripts/install-all.sh: it runs every platform script in sequence (each isolated, so one failing toolchain does not abort the rest) and prints a per-platform PASS/FAIL summary (Google Workspace is skipped, not failed, until a Google OAuth client JSON is saved: it needs its own --client-json).
  2. Supply the platform’s credentials (see its skill) and run the printed claude mcp add --scope user … command. WhatsApp additionally needs its bridge running + an interactive QR scan before the server works.
  3. Restart Claude Code so the stdio server loads.

Per-platform env vars / auth live in each t1k-comms-mcp-<platform> skill. To pick a destination from a free-form “send / post / notify” request, the t1k-comms-mcp-core-router agent resolves it to the right platform.

  • Fork-as-source. Never vendor or copy server code into this repo; the fork is canonical.
  • Never commit secrets. Tokens, OAuth secrets, and WhatsApp session files stay in local env / gitignored config.
  • Confirm before sending to any live channel or DM.
  • Readiness hook only reminds. The MCP-readiness check (check-mcp-health.cjs) reminds, at most once per 7 days per optional server, gated to sessions where the matching module is installed, to run install-<platform>.sh when an expected server is unregistered. It never builds, registers, or removes anything; you run the script with credentials when ready.