A setup process for MCP servers, which are connections that let a coding agent work with external services, based on the project's chosen technology stack.

Use it after defining the architecture or when adding services such as a database, payments, email, deployment, design, monitoring, or task-management integration.

It checks the official instructions, existing server status, scope, and credentials before adding an integration, reducing configuration mistakes.

How polmarza/project-template configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to polmarza/project-template. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/polmarza/project-template/main/.claude/skills/mcp-setup/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/polmarza/project-template

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/polmarza/project-template/mcp-setup/github.svg)](https://agentmods.dev/skills/polmarza/project-template/mcp-setup)

Your own site

<a href="https://agentmods.dev/skills/polmarza/project-template/mcp-setup"><img src="https://agentmods.dev/badge/skills/polmarza/project-template/mcp-setup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/polmarza/project-template/mcp-setup"><img src="https://agentmods.dev/badge/skills/polmarza/project-template/mcp-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,130 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00073	$0.01130
Opus 5.5	$0.00029	$0.00452
Sonnet 5.5	$0.00015	$0.00226
Haiku 4.5	$0.00007	$0.00113

Measured 14d ago against content hash ca027cd6f292, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mcp-setup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 14d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/mcp-setup/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Configura los servidores MCP de este proyecto según el stack definido en docs/architecture.md.

Sigue el "Protocolo de MCPs" de AGENTS.md. Esta skill lo lanza a demanda; el flujo normal es que se ejecute solo al terminar la arquitectura o al añadir una integración nueva.

1. Contexto

Lee docs/architecture.md. Si el stack todavía no está definido, dilo y para aquí: sin stack no hay nada que decidir.
Ejecuta claude mcp list para ver qué servidores hay ya disponibles y en qué estado están.

2. Averigua qué existe

Por cada servicio del stack (base de datos, emails, pagos, despliegue, diseño, observabilidad, gestión de tareas…), determina si publica un servidor MCP.

Si no estás seguro de que exista, de cómo se llama el paquete, de qué transporte usa o de qué credenciales pide, búscalo en la documentación oficial del servicio antes de proponerlo. No inventes comandos ni nombres de variables de entorno: un claude mcp add mal copiado deja un servidor que no arranca y cuesta más depurarlo que buscarlo bien a la primera.

Como fuente vale el dominio del proveedor o su repositorio oficial, nada más. Un blog, un agregador de MCPs o un gist no son fuente válida para un comando que se va a ejecutar en la máquina del usuario: un paquete typosquatteado se ejecuta con npx exactamente igual que el legítimo. Si solo lo encuentras en fuentes no oficiales, dilo y que decida el usuario.

Descarta los servicios sin MCP sin darles vueltas.

3. Pregunta

Presenta la lista de candidatos y, por cada uno, pregunta con qué alcance lo quiere:

Alcance	Dónde vive	Quién lo ve	Cuándo usarlo
Global (`user`)	`~/.claude.json`	Solo el usuario, en todos sus proyectos	Ya lo tiene configurado o lo usa en todas partes. No se toca nada del repo
Proyecto (`project`)	`.mcp.json`, commiteado	Todo el equipo	Recomendado: el servidor forma parte del proyecto y el equipo lo hereda
Local (`local`)	`~/.claude.json`, bajo la ruta del proyecto	Solo el usuario, solo aquí	Pruebas o credenciales que no quiere ni referenciadas en el repo

Read the full file on GitHub · 88 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

14d ago Changed ca027cd6f292
29d ago First seen · 88 lines · 73 tokens per session scan A 4f8198590874

Subscribe to this mod's changes

mcp-setup is a skill published in the GitHub repository polmarza/project-template (89 stars, last pushed 15d ago), licensed MIT. It adds 73 tokens to every session and 1,130 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-08.

Building agents Cloud DevOps and cloud showcase

mcp-setup next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
mcp-setuppolmarza/project-template	Skill	89	15d ago	MIT	A	73	Claude Code
gke-compute-classesgoogle/skills	Skill	22k	yesterday	Apache-2.0	A	83	Claude Code, Codex
gke-reliabilitygoogle/skills	Skill	22k	yesterday	Apache-2.0	A	85	Claude Code, Codex
gke-workload-securitygoogle/skills	Skill	22k	yesterday	Apache-2.0	A	171	Claude Code, Codex
cloud-architectJeffallan/claude-skills	Skill	12k	7d ago	MIT	A	71	Claude Code
nemo-automodel-launcher-configNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	30	Claude Code
azure-mgmt-botservice-dotnetmicrosoft/skills	Skill	3.2k	yesterday	MIT	A	78	Claude Code

project-template: Skill for Claude Code