mcp-setup

mcp-setup is a skill for Claude Code, Codex from jpoutrin/product-forge. It costs 56 tokens per session (1,472 once invoked), scanned A, original, MIT.

A setup guide for connecting Claude Code to outside tools and services through MCP, an open standard for giving AI assistants access to tools, databases, and APIs.

In plain words
What is it for?
Use it to configure HTTP, SSE, or local-process MCP servers for services such as issue trackers, databases, monitoring tools, design tools, or communication apps.
Why use it?
It removes the need to work out server types, connection commands, and authentication details each time you connect an external service.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the claude-code-dev plugin — 17 skills, 2 hooks shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/jpoutrin/product-forge/mcp-setup
Any agent
npx skills add jpoutrin/product-forge --skill mcp-setup
Clone the repo
git clone --depth 1 https://github.com/jpoutrin/product-forge

Made for: Claude Code, Codex.

Or install claude-code-dev, the plugin that ships this one along with the rest of its 17 skills, 2 hooks.

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.

agentmods badge for mcp-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpoutrin/product-forge/mcp-setup.svg)](https://agentmods.dev/skills/jpoutrin/product-forge/mcp-setup)
Your own site
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/mcp-setup"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/mcp-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,472 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00056 $0.01472
Opus 5 $0.00028 $0.00736
Sonnet 5 $0.00011 $0.00294
Haiku 4.5 $0.00006 $0.00147

Measured 4d ago against content hash fea71a841558, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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.

plugins/claude-code-dev/skills/mcp-setup/SKILL.md · 216 lines

How it starts

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

MCP Setup Skill

This skill helps configure Model Context Protocol (MCP) servers to connect Claude Code to external tools, databases, and APIs.

What is MCP?

MCP (Model Context Protocol) is an open-source standard for AI-tool integrations. MCP servers give Claude Code access to:

  • Issue trackers (Jira, GitHub Issues)
  • Monitoring tools (Sentry, Statsig)
  • Databases (PostgreSQL, MySQL)
  • Design tools (Figma)
  • Communication (Slack, Gmail)
  • And hundreds more

Server Types

1. HTTP Servers (Recommended for remote)

Cloud-based services, most widely supported.

claude mcp add --transport http <name> <url>

# Example: Connect to Notion
claude mcp add --transport http notion https://mcp.notion.com/mcp

# With Bearer token authentication
claude mcp add --transport http secure-api https://api.example.com/mcp \
  --header "Authorization: Bearer your-token"

2. SSE Servers (Deprecated)

Use HTTP instead where available.

claude mcp add --transport sse <name> <url>

# Example: Connect to Asana
claude mcp add --transport sse asana https://mcp.asana.com/sse

3. Stdio Servers (Local processes)

Run as local processes on your machine.

claude mcp add --transport stdio <name> <command> [args...]

# Example: Airtable server
claude mcp add --transport stdio airtable --env AIRTABLE_API_KEY=YOUR_KEY \
  -- npx -y airtable-mcp-server

# Example: PostgreSQL database
claude mcp add --transport stdio db -- npx -y @bytebase/dbhub \
  --dsn "postgresql://user:pass@localhost:5432/mydb"

Note: The -- separates Claude's flags from the server command.

Configuration Scopes

Scope Storage Use Case
local ~/.claude.json (project path) Personal, project-specific
project .mcp.json in project root Team-shared via git
user ~/.claude.json (global) Personal across all projects
# Add to specific scope
claude mcp add --transport http api --scope project https://api.example.com

Read the full file on GitHub · 216 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.

  1. 4d ago First seen · 216 lines · 56 tokens per session scan A fea71a841558

Subscribe to this mod's changes

mcp-setup is a skill published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It adds 56 tokens to every session and 1,472 once invoked, about $0.0003 per session on Opus 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-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens