Plug your AI into the team (MCP)

Teamping is a team context layer where developers and non-developers (AI builders) collaborate in their own role's language. This one page is enough to connect your AI (Claude Code · Cursor · Claude Desktop) to the team workspace.

Once connected, your AI reads and writes the team's work (manifests) · meetings · chat · roadmap through tools.

Easiest way — the AI setup kit. After signing in, use "Download setup kit" on My page to get one file and give it to the AI you use (Claude Code · Codex). The AI does the steps below for you, asking as it goes.

Let your AI do it (easiest)

Give the file from "Download setup kit" on My page to your AI (Claude Code · Codex) and say:

"Set up Teamping following this teamping-setup.md file."

Never paste your key (token) into the chat — chat history keeps it forever. The kit tells you how to add the key separately.

With the kit, your AI asks at each step and does the setup for you, telling you when it's your turn (issuing the key · restarting the app · approving). Only when setting up by hand without the kit, follow Step 2 below — and even then, enter the key yourself and never tell it to the AI.

Step 1 — Issue a key (30 seconds)

Log in to teamping.dev (the email your team invited)
My page → Connect your AI → "Issue new key"
Copy the plaintext key (teamping_...) — it is shown only once (close the window and it is gone)

Never share the key. If it leaks, revoke it on My page and issue a new one. Scopes are submit (submit work) and list (read) only — risky actions like reviewing completion reports or managing the team are impossible with a key (people do them on the web). Exception: an owner/admin submit key can confirm/reject (delete drafts) and change progress, assignee and commit links on the roadmap.

Step 2 — Connect

A. Claude Code (CLI) or the Cursor·VSCode extension ← recommended for developers

Option 1 — one command (in the project folder):

claude mcp add --transport http teamping https://teamping.dev/mcp \
  --header "Authorization: Bearer teamping_YOUR_TOKEN"

Option 2 — a .mcp.json file (create/add at the project root):

{
  "mcpServers": {
    "teamping": {
      "type": "http",
      "url": "https://teamping.dev/mcp",
      "headers": {
        "Authorization": "Bearer teamping_YOUR_TOKEN"
      }
    }
  }
}

B. Claude Desktop app (Mac / Windows)

Add the block below to the config file. If you already have other MCPs, put only mcpServers inside teamping.

File location — Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Requires: Node.js installed (check with node -v)

{
  "mcpServers": {
    "teamping": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://teamping.dev/mcp",
        "--header",
        "Authorization:${TEAMPING_AUTH}"
      ],
      "env": {
        "TEAMPING_AUTH": "Bearer teamping_YOUR_TOKEN"
      }
    }
  }
}

mcp-remote is a small bridge between the desktop app (local) and our remote server (HTTP). It installs itself on first run. It matters that the token lives in env — if you hard-code it like --header "Authorization: Bearer TOKEN", the token shows in the process list (ps) in plaintext the whole time the app runs. Tighten the config file too: chmod 600. Note the {"type":"http", ...} form in A above is Claude Code only — the desktop config ignores it.

C. Codex (CLI · desktop app) — quick connect, no key

Codex doesn't need a copied key. Run this line in a terminal and a browser opens.

codex mcp add teamping --url https://teamping.dev/mcp

Sign in to Teamping in the browser, choose a project and press "Allow". Then open Codex in a new session and it's connected. Run codex mcp login teamping only when a connection you already added has dropped — running it right after adding asks for consent a second time.

Step 3 — Verify

Claude Desktop: quit fully (⌘Q) and restart
Claude Code: restart the session (or run claude mcp list and look for teamping)

Then ask your AI: "show me the teamping tools" or "what's my work (get_my_work)" → if the tools below appear, you're connected

What you can do (tools)

Tool	What it does
`submit_manifest`	Submit the work you just did to the channel as a standard report (manifest)
`list_manifests · get_manifest`	Read the channel's work reports (role-translated views)
`get_my_work`	See what's assigned to me and what's waiting for review
`propose_stage_change · propose_due_change`	Propose a stage or due-date change
`respond_to_manifest`	Ask, comment on, or request changes to someone's work
`start_thread · post_thread_message · list_thread(_messages)`	Brainstorming meetings (threads)
`post_channel_message · list_channel_messages`	Always-on channel chat
`propose_milestones`	Propose roadmap phase drafts (people confirm on the web — or with the tool below)
`update_roadmap_node`	Confirm · reject · progress status · assignee · commit link on the roadmap (owner/admin's AI · instructed to use it only when asked)

People review completion reports on the web. There is no tool that reviews work (a design invariant). Only the roadmap can be changed — by an owner/admin's AI when they ask (a rule the tool instructions carry; the server cannot tell who asked); a compromised AI cannot rewrite the rest of the team state.

Troubleshooting

Tools don't show up → check you fully quit and restarted the app / the key is exact (no surrounding spaces, no Bearer prefix)
401·403 / auth failed → the key expired or was revoked. Issue a new one on My page
Desktop doesn't work → check Node with node -v (mcp-remote needs Node)

Teamping — the two-way communication tool that removes the wall between developers and AI builders. Everyone sees and edits the same GitHub code in their role's language; AI translates, people approve.