MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Use as the agents build stage of the Butterbase journey. An agent skill from butterbase-ai/butterbase-skills.
Install Journey Agents
$ npx skills add butterbase-ai/butterbase-skills --skill journey-agents -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install butterbase-ai/butterbase-skills journey-agents --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/journey-agents .claude/skills/journey-agents && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "journey-agents" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-agents into .claude/skills/journey-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-agents", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-agentsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add butterbase-ai/butterbase-skills --skill journey-agents -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install butterbase-ai/butterbase-skills journey-agents --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/journey-agents .agents/skills/journey-agents && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "journey-agents" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-agents into .agents/skills/journey-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-agents", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add butterbase-ai/butterbase-skills --skill journey-agents -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install butterbase-ai/butterbase-skills journey-agents --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/journey-agents .cursor/skills/journey-agents && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "journey-agents" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-agents into .cursor/skills/journey-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-agents", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/butterbase-ai/butterbase-skills.git --path skills/journey-agents--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add butterbase-ai/butterbase-skills --skill journey-agents -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install butterbase-ai/butterbase-skills journey-agents --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/journey-agents .gemini/skills/journey-agents && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "journey-agents" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-agents into .gemini/skills/journey-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-agents", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install butterbase-ai/butterbase-skills journey-agentsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add butterbase-ai/butterbase-skills --skill journey-agents -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/journey-agents .github/skills/journey-agents && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "journey-agents" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-agents into .github/skills/journey-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-agents", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add butterbase-ai/butterbase-skills --skill journey-agents -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install butterbase-ai/butterbase-skills journey-agents --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/butterbase-ai/butterbase-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/journey-agents .opencode/skills/journey-agents && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "journey-agents" agent skill from https://github.com/butterbase-ai/butterbase-skills/tree/main/skills/journey-agents into .opencode/skills/journey-agents/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "journey-agents", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
journey-agents- GitHub stars
- 534
- Token cost
- ~1.2k tokens
- SKILL.md length
- 602 words
- Files
- 1
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use as the agents build stage of the Butterbase journey. An agent skill from butterbase-ai/butterbase-skills.
- Works in 6 steps: Refresh docs. Call butterbase_docs with… → Register MCP servers first. For each MCP… → Build each agent. For each agent in the… → …
- Tasks that involve MCP servers
- SKILL.md covers When to use, Preflight, Inputs and Procedure, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Journey Agents is an agent skill from butterbase-ai/butterbase-skills. Use as the agents build stage of the Butterbase journey. Implements the Agents section of 02-plan.md by delegating to the agents skill for each agent. Registers any required MCP servers, validates each graphspec, creates the agent, and smokes it via invokeagent. Skipped if the plan has no agents.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: Plugin for Butterbase.ai. The licence is MIT.
When your agent uses it
- Tasks that involve MCP servers
Example prompts
- “/journey-agents”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Refresh docs. Call butterbase_docs with topic: "agents". If the cache (docs/butterbase/03b-docs-cache.md) already covers agents, skip.
- Register MCP servers first. For each MCP server in the plan
- Build each agent. For each agent in the plan, in order
- Persist specs to the repo. Confirm agents/.json files are tracked locally. They will be carried by butterbase repo push (run by the…
- Tick state. Mark - [x] agents in 00-state.md, set current_stage to the next unchecked stage.
- Return to journey orchestrator (or ask "Continue to the next stage? (yes/no)").
What it can do on your machine
Read from SKILL.md and the folder at commit aa8ae69. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Journey Agents loads about 1.2k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 602 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from butterbase-ai/butterbase-skills at commit aa8ae69, republished under its MIT licence (© butterbase-ai). 602 words, ~1,216 tokens.
Download SKILL.mdSave it as
.claude/skills/journey-agents/SKILL.md (or your agent's skills folder).- name
- journey-agents
- description
- Use as the agents build stage of the Butterbase journey. Implements the Agents section of 02-plan.md by delegating to the `agents` skill for each agent. Registers any required MCP servers, validates each graph_spec, creates the agent, and smokes it via invoke_agent. Skipped if the plan has no agents.
Journey: Agents
Build the agents described in 02-plan.md. Order: MCP servers first (probe must pass before any agent references them) → agents → smoke runs.
When to use
- Dispatched by
journeywhencurrent_stage: agents. - Directly via
/butterbase-skills:journey-agents. - Skipped (annotated
(n/a)) if the plan lists no agents.
Preflight
If docs/butterbase/03-preflight.md is missing, older than 24 hours, or 00-state.md has app_id: null, invoke butterbase-skills:journey-preflight first. Wait for it to return successfully before proceeding.
Inputs
docs/butterbase/02-plan.md— the Agents section (names, purpose, tool list, visibility, MCP servers needed).docs/butterbase/00-state.md— forapp_id.- Any handcrafted spec files under
agents/in the project (preferred — version-controlled and survives clones).
Procedure
Refresh docs. Call
butterbase_docswithtopic: "agents". If the cache (docs/butterbase/03b-docs-cache.md) already covers agents, skip.Register MCP servers first. For each MCP server in the plan:
- Print:
"Registering MCP server '<label>' at <url> (transport=<sse|http|streamable_http>). Proceed?". Wait foryes. - Call the MCP-servers registration route (or the dashboard's MCP Servers page if a wrapping MCP tool is not yet available — check
butterbase_docstopicagentsfor the current preferred path). - Wait for probe result. If
status: unhealthy, surface the error and ask the user to fix (URL, auth header, transport mismatch) before continuing. Do not create agents that reference an unhealthy server.
- Print:
Build each agent. For each agent in the plan, in order: a. Print:
"About to build agent: <name> (visibility=<v>, tools=<n builtin / m mcp / k function>). Proceed?". Wait foryes. b. Invokebutterbase-skills:agentsvia the Skill tool with: agent name, intended behaviour, plan-derived tool list, model preference, visibility/limits. The wrapped skill drafts thegraph_spec, writes it toagents/<name>.jsonin the project repo, and callsvalidate_agent_spec. c. If validation fails, surface the Zod issues and loop the agents skill to fix. d. Safety gate. Ifvisibility != 'private'AND any node can reach a write tool (insert_row,update_row,delete_row,write_storage, or anyread_write-mode MCP/function tool), explicitly ask:"This agent is reachable by <visibility> callers and can write data. Set safety_acknowledged=true? (yes / change to private / reduce tools)". Do not proceed silently. e.create_agentwith the validated spec. f. Smoke:invoke_agentwith a representative input. Pollget_agent_rununtil terminal. If the run errors, debug per theagentsskill's debugging procedure; otherwise show the user the final output. g. Append one line per agent todocs/butterbase/04-build-log.md:<ISO timestamp> agents create_agent <agent-name> ok (run smoke=<run_id>)Persist specs to the repo. Confirm
agents/<name>.jsonfiles are tracked locally. They will be carried bybutterbase repo push(run by thetemplatesstage if the user is publishing, or any time the user pushes a snapshot). This is the only way a clone recipient can recreate the agents — theagentstable is not part of clone replay.Tick state. Mark
- [x] agentsin00-state.md, setcurrent_stageto the next unchecked stage.Return to
journeyorchestrator (or ask"Continue to the next stage? (yes/no)").
Show full SKILL.md (135 more words)Show less
Outputs
- One or more agents created against the live app.
- One or more
agents/<name>.jsonspec files in the project repo. - One line per agent in
docs/butterbase/04-build-log.md.
Anti-patterns
- ❌ Skipping
validate_agent_spec. Bad specs surface as opaque runtime errors after the agent is live. - ❌ Creating a
publicwrite-capable agent without rate limits or adaily_budget_usd. The runtime requiressafety_acknowledged, but you should also pick hourly per-IP and per-app caps. - ❌ Hard-coding secrets in
system_promptorargs_template. Read them fromctx.envinside a function tool. - ❌ Forgetting that the
agentstable is not replayed on clone. Always commit the spec JSON and document re-import (butterbase agents create -f agents/<name>.json) in the README. - ❌ Smoking with
visibility: 'private'and calling it good for apublicagent. After the smoke, change visibility and re-test with an unauthenticated curl to confirm the public path works.
© butterbase-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/journey-agents of butterbase-ai/butterbase-skills.
Open the folder on GitHubat commit aa8ae69
Compare with similar skills
Journey Agents next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Journey Agents this skillbutterbase-ai/butterbase-skills | 534 | — | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 4 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Context Mode Output Sandboxmksglu/context-mode | 26k | — | ~4.1k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
MCP Server Builder
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
- Official
MCP Integration for Plugins
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
Crush Configuration
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
Context Mode Output Sandbox
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
Warp GUI to Agent CLI Migration
warpdotdev/warp
Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.
More from butterbase-ai/butterbase-skills
All 39 skills in this repoAI
butterbase-ai/butterbase-skills
A skill your agent uses when calling the app's AI gateway from agent tools — chat completions, embeddings, listing models, configuring defaults or BYOK, reading token/cost usage
Auth Setup
butterbase-ai/butterbase-skills
A skill your agent uses when configuring OAuth providers (Google/GitHub/Apple/X/etc.), setting up post-login auth hooks, tuning JWT lifetimes, or generating service API keys
Build App
butterbase-ai/butterbase-skills
A skill your agent uses when building a new Butterbase app from scratch, creating a full-stack application, or when the user asks to set up a complete backend with database, auth, and deployment
Contributing
butterbase-ai/butterbase-skills
A skill your agent uses when contributing to the Butterbase codebase, adding new MCP tools, creating API routes, writing migrations, or understanding the monorepo architecture
Debug Rls
butterbase-ai/butterbase-skills
A skill your agent uses when users report access denied errors, see wrong data, RLS policies are not working, or when troubleshooting Row-Level Security issues in Butterbase
Deploy Frontend
butterbase-ai/butterbase-skills
A skill your agent uses when deploying a frontend (React, Next.js, or static HTML) to a live URL on Butterbase, or when troubleshooting deployment issues like MIME type errors or blank pages
Related
Works with
Categories
Questions about Journey Agents
What does Journey Agents do?
Use as the agents build stage of the Butterbase journey. An agent skill from butterbase-ai/butterbase-skills. Journey Agents is an agent skill from butterbase-ai/butterbase-skills. Use as the agents build stage of the Butterbase journey.
When should I use Journey Agents?
Journey Agents fits situations like: tasks that involve MCP servers.
How do I install Journey Agents in Claude Code?
Run `npx skills add butterbase-ai/butterbase-skills --skill journey-agents -a claude-code`. Or copy the skill folder (skills/journey-agents in butterbase-ai/butterbase-skills) into .claude/skills/journey-agents in your project. Claude Code loads it when a task matches its description.
How do I install Journey Agents in Codex?
Run `npx skills add butterbase-ai/butterbase-skills --skill journey-agents -a codex`. Or copy the skill folder (skills/journey-agents in butterbase-ai/butterbase-skills) into .agents/skills/journey-agents in your project. Codex loads it when a task matches its description.
Can I use Journey Agents in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add butterbase-ai/butterbase-skills --skill journey-agents -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/journey-agents, .gemini/skills/journey-agents, .github/skills/journey-agents and .opencode/skills/journey-agents in your project.
What does Journey Agents need to run?
SKILL.md names no scripts, command-line tools or credentials: Journey Agents is instructions for the agent only.
Does Journey Agents access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Journey Agents safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Journey Agents use?
Journey Agents is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Journey Agents use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Journey Agents?
Skills that share tags, products or a category with Journey Agents: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Crush Configuration (charmbracelet/crush, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Journey Agents?
butterbase-ai (a GitHub organization) maintains it in butterbase-ai/butterbase-skills, which has 534 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 5, 2026.
Source: butterbase-ai/butterbase-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.