← ClaudeAtlas

add-mcp-skilllisted

Add a new BigQuery-backed skill to the MCP server: a tool exposed to AI agents plus the .md context files that describe the underlying data. Invoke when the user wants AI agents (claude.ai, Claude Code, Cursor) to query a new domain of the warehouse.
pol-cc/agentic-data-engineer · ★ 0 · AI & Automation · score 72
Install: claude install-skill pol-cc/agentic-data-engineer
# add-mcp-skill > **Status**: v0.9.0 — folder-pattern reference written (the most important component) and the runnable MCP server skeleton (`templates/mcp-skeleton/`) is now included (FastMCP `server.py` with read tools always-on and write tools **off by default**). **Write tools are safe-by-default: off unless `MCP_WRITE_TOOLS=on`, and when on they OPEN A PR for human review rather than pushing to `main`** (the server feeds untrusted synced data to an agent — see [`references/mcp-github-writeback.md`](references/mcp-github-writeback.md), "Security posture"). Docker/compose/deploy and a working `example-sales` skill ship too. Step-by-step playbook for adding a skill to an existing MCP server still skeletal. ## What this skill does Extends the client's MCP server with a new "skill" — a callable tool plus its context. After this skill runs, an AI agent connected to the MCP server can answer natural-language questions about the new data domain, generate the right SQL, and execute it against BigQuery. The pattern mirrors `pol-cc/skills-sapiens` (the reference MCP deployment): one MCP server, multiple skills, each scoped to a domain (sales, finance, marketing, etc.). ## Preflight ```bash if [ ! -f .agentic-data-engineer.json ]; then echo "[abort] not a managed MDS deployment" exit 1 fi jq -e '.stack.mcp == true' .agentic-data-engineer.json > /dev/null || { echo "[abort] this MDS doesn't have an MCP server" echo "run Phase 3 of create-mds first" exit 1 } ``` ## A