mcp-setup
Skill9 starsChanged 6 months agoMITView on GitHub
Configure MCP server, daemon, scaffolding, or doctor. Use when setting up XcodeBazelMCP for other projects, configuring the daemon, running doctor, or working on project scaffolding templates.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- naman10parikh/pennytheir own version, first seen Nov 8, 2026
- naman10parikh/wikimemtheir own version, first seen Nov 8, 2026
- naman10parikh/turbotheir own version, first seen Oct 25, 2026
- naman10parikh/pixeltheir own version, first seen Oct 25, 2026
- jonmumm/skillstheir own version, first seen Oct 21, 2026
- naman10parikh/agentgridtheir own version, first seen Oct 20, 2026
Used with
Projects with it also use ecosystem-reference, fractal-delegation and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
naman10parikhSkillecosystem-reference
Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.
Also in 5 projects that use this
naman10parikhSkillfractal-delegation
Also in 5 projects that use this
KirchliveSkillskill-routing
Decides which of the installed skills a task needs and loads them before the work starts. This skill should be used at the beginning of any multi-step task — build, fix, refactor, migrate, review, plan, release, research, write, design, video — and again at every phase change, after context compaction, and when work moves into a different part of the codebase. Use it for requests like "let's build X", "fix this bug", "refactor Y", "plan the migration", "review this", and also when the user asks which skill applies, why a skill did not fire, or asks to check what is available.
Also in 5 projects that use this
sublimotionSkillagent-runtime
Launch and manage detached agent runs on EKS via the agent-runner CLI. Use when the user says "launch an agent run", "agent runtime", "agent-runner", "run this spec on the cluster", "check run status", "agent run logs", or "stop a run". Do NOT use for writing the agent-runner code itself (edit the sibling ../agent-runner repo), Terraform of the foundation (use terraform-automation), or GPU serving deployments (use infra-deployer).
Also in 5 projects that use this
GoZippySkillrepo-scout
Also in 5 projects that use this
BenjaminGSkillharness-review
Turn one PR's review comments into harness fixes — classify each cause by the most solid place it can live (codebase, lint, rules, skill), then draft the fixes in a separate PR.
Also in 5 projects that use this
- +6 more from naman10parikh
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- thejaustin/ShizukuPlus★ 1.7ksame name
- vellum-ai/vellum-assistant★ 1.5ksame name
- babamba2/superclaude-for-sap★ 73same name
- ingpoc/SKILLS★ 9same name
- naman10parikh/agentgrid★ 9same name
- mintorain/mintorain-tmux-ocastra★ 8same name
- naman10parikh/wikimem★ 8same name
- hajekim/agentic-design-patterns-skills★ 4same name
- AzamatRaimbekov/vibe-coding-mentor★ 3same name
- jonmumm/skills★ 2same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- cli-developmentSkill
- device-and-uiSkill
- example-projectSkill
- simulator-workflowSkill
- swift-agent-debug-logSkill
- tool-handler-developmentSkill
- swift-agent-debug-logSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
After source changes, run npm run build to update dist/.
- Very specific: line 26
Prefer absolute paths — ~ may not expand in all MCP clients.
- Very specific: line 50
Test-only templates generate BUILD.bazel under ${name}Tests/ subdirectory.
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
MCP Setup & Configuration
Using in Other Projects
The package is not published to npm (private: true). Use the local dist/cli.js path in .cursor/mcp.json:
{
"XcodeBazelMCP": {
"command": "node",
"args": ["/Users/matheus.gois/Projects/XcodeBazelMCP/dist/cli.js", "mcp"],
"env": { "BAZEL_IOS_WORKSPACE": "/path/to/your/workspace" }
}
}- After source changes, run
npm run buildto updatedist/. - Prefer absolute paths —
~may not expand in all MCP clients. - Local Bazel execution is the default.
BITRISE_BUILD_CACHE_AUTH_TOKENis not required. Bitrise RBE configs (bitrise,remote_linux) are stripped automatically unless the token is set.
Config File
.xcodebazelmcp/config.yaml (in workspace root or ~/.xcodebazelmcp/):
enabledWorkflows— comma-separated workflow IDs (e.g.build, test, simulator)profiles:— nested blocks for per-project defaultsactivateProfilemerges profile defaults into session defaults
Per-Workspace Daemon
- Unix socket:
/tmp/xbmcp-daemon-<sha256(wsPath)[0:12]>.sock - PID file:
~/.xcodebazelmcp/daemons/<hash>.json - JSON protocol:
ping,status,list_ops,register_op,unregister_op,shutdown - Client spawns detached child via
child.unref()withXBMCP_DAEMON=1env, polls up to 5s for socket. - Auto-cleanup on
SIGTERM/SIGINT: removes socket and PID file.
Project Scaffolding
6 templates: ios_app, ios_test, ios_app_with_tests, macos_app, macos_test, macos_app_with_tests.
- Guards against overwriting — fails if
MODULE.bazelorWORKSPACEalready exists. - Test-only templates generate BUILD.bazel under
${name}Tests/subdirectory. - Scaffold
namevalidated with^[A-Za-z][A-Za-z0-9_-]*$to prevent path traversal.
Doctor
Reports: system info (platform, arch, CPUs, memory, Node), workspace details (path, config, MODULE.bazel/WORKSPACE/.bazelrc), dependency versions (bazel, xcode, simctl), full tool inventory by workflow with enabled/disabled status.
Dependency checks run in parallel via Promise.all.
Smoke Testing
scripts/smoke.mjs reads tool names from individual handler files under src/tools/handlers/ (not bazel-tools.ts which only aggregates).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

