How to share Claude Code skills and MCP servers with your whole team

Publish your skills and deploy your MCP servers to a spawnpoint team. A skill one member publishes there shows up for every member's agent, and the team page gives each person one line that adds the team's MCP servers and skills to their Claude Code or Codex.

A skill is a set of written instructions for a task: how your team writes the weekly report, how it names files, which checks to run before a customer email goes out. An MCP server is a small program that agents can ask for things, like a customer's history in your CRM. Both help one person, and they help more when everyone's agent uses the same ones.

To share a skill, ask your agent to publish it to the team: "Publish my weekly-report skill to the team." From then on, every member's agent that is signed in for the team sees it in the team's list, and fetches and follows it when a task calls for it. Publishing a skill with the same name again replaces it with the new version. spawnpoint refuses a skill with an API key written into it.

To share an MCP server, have your agent build it and deploy it for the team like any other app. It shows up on the team page, it opens only for team members unless someone shares it further, and each member's agent signs in to it once.

New members get both at once. The team page gives each member an install line that connects their coding agent to spawnpoint and adds the team's MCP servers and skills to Claude Code and Codex. Running it again picks up ones added since. Each line works once, for 15 minutes, so a line left behind in a terminal's history stops working soon after.

A skill written with Claude Code works for a coworker who uses Codex, because the skill is stored with the team, where every member's agent can fetch it.