agentmods.dev

setup-mcp

setup-mcp is a skill for Claude Code, Codex from asysta-act/agent-flow. It costs 16 tokens per session (5,740 once invoked), scanned B, original, MIT.

A setup command for connecting a developer environment to external services used by an agent workflow. MCP servers are connections that let an agent use outside tools or services.

In plain words
What is it for?
Use it to create or update MCP server settings, configure optional tracker and repository details, set tool permissions, and update the project’s gitignore file.
Why use it?
It avoids manually creating the configuration files and permissions needed for those connections. It also keeps sensitive MCP configuration out of version control when appropriate.

Skill for Claude CodeCodex

Part of the agent-flow plugin — 17 skills, 17 agents shipped together

not rated 12 1mo ago B scan 16 tokens original MIT
View the source file asysta-act/agent-flow
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/asysta-act/agent-flow/setup-mcp
Any agent
npx skills add asysta-act/agent-flow --skill setup-mcp
Clone the repo
git clone --depth 1 https://github.com/asysta-act/agent-flow

Made for: Claude Code, Codex.

Or install agent-flow, the plugin that ships this one along with the rest of its 17 skills, 17 agents.

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 setup-mcp

README.md
[![agentmods](https://agentmods.dev/badge/skills/asysta-act/agent-flow/setup-mcp.svg)](https://agentmods.dev/skills/asysta-act/agent-flow/setup-mcp)
Your own site
<a href="https://agentmods.dev/skills/asysta-act/agent-flow/setup-mcp"><img src="https://agentmods.dev/badge/skills/asysta-act/agent-flow/setup-mcp.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,740 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 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.00016 $0.05740
Opus 5 $0.00008 $0.02870
Sonnet 5 $0.00003 $0.01148
Haiku 4.5 $0.00002 $0.00574

Measured 3d ago against content hash bf4513ea14b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

setup-mcp scanned grade B with 2 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 3d 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.

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

You can edit .mcp.json manually later with your token.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sfL -o ~/.claude/bin/{asset_name} "https://gitea.com/gitea/gitea-mcp/releases/download/v1.1.0/{asset_name}"
skills/setup-mcp/SKILL.md · 396 lines

How it starts

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

Init

Set up the developer environment for agent-flow pipeline. Generates .mcp.json (MCP server configuration) and .claude/settings.json (tool permissions).

This command is the counterpart to /agent-flow:onboard:

  • onboard = project config (Automation Config in CLAUDE.md)
  • init = developer environment (MCP servers, tokens, permissions)

Input: $ARGUMENTS = (none) | --update | --tracker-type <type> | --tracker-instance <url> | --sc-remote <owner/repo> (flags may be combined)

Scope

This command writes to the CURRENT WORKING DIRECTORY:

  • .mcp.json — MCP server configuration
  • .claude/settings.json — tool auto-approval (optional)
  • .gitignore — adds .mcp.json if not present

Step 0: Parameter Override

Parse $ARGUMENTS for optional CLI flags:

  • --tracker-type <type> → cli_tracker_type
  • --tracker-instance <url> → cli_tracker_instance
  • --sc-remote <owner/repo> → cli_sc_remote

If ANY of these flags is provided:

  1. Validate --tracker-type (if provided) against the lookup table in ../../core/mcp-detection.md Process step 1. Valid values: youtrack, github, jira, linear, gitea, redmine. If invalid → error: "Invalid tracker type '{value}'. Valid types: youtrack, github, jira, linear, gitea, redmine."
  2. Skip Step 1 (Automation Config read). Use flag values instead:

    • Type = cli_tracker_type (if not provided, infer from cli_sc_remote hostname: github.com → github; otherwise → error: "--tracker-type is required when CLAUDE.md is not available.")

    • Instance = cli_tracker_instance (if not provided, derive default:

      Path note: trackers.md lives in the plugin installation directory. Resolve via Glob before reading defaults.

      Resolve {trackers_md_path}: Glob .claude/plugins/**/docs/reference/trackers.md (prefer path containing .claude/plugins/ or agent-flow/); fallback **/docs/reference/trackers.md; last resort docs/reference/trackers.md. If not found → use hardcoded defaults per tracker type. Read the Instance & Project Defaults table from {trackers_md_path} for the given type.)

    • Remote = cli_sc_remote (if not provided, skip SC server — tracker-only setup)

  3. Proceed to Step 1b (detect .mcp.json.example) with the overridden values.

Read the full file on GitHub · 396 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. 3d ago First seen · 396 lines · 16 tokens per session scan B bf4513ea14b3

Subscribe to this mod's changes

setup-mcp is a skill published in the GitHub repository asysta-act/agent-flow (12 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 5,740 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (reads mcp configuration, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

agentsaiautomationbug-fixclaude-codepipeline
Related

Other skills, from other repositories

cortivex-pipeline

Build and run AI agent pipelines that decompose complex tasks into coordinated agent workflows.

AhmedRaoofuddin/Cortivex · 22 tokens

stream-chain

Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows.

spencermarx/open-code-review · 18 tokens

bare-eval

Run isolated eval and grading calls using CC 2.1.81 --bare mode. Constructs claude -p --bare invocations for skill evaluation, trigger testing, and LLM grading without plugin/hook interference. Use when running eval pipelines, grading skill outputs, benchmarking prompt quality, or testing trigger accuracy in isolation.

yonatangross/orchestkit · 69 tokens

chain-patterns

Chain patterns for multi-phase pipelines: MCP detection, handoff files, checkpoint-resume, worktree agents, CronCreate monitoring. Use when building or debugging a pipeline skill.

yonatangross/orchestkit · 39 tokens

fix-issue

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…

yonatangross/orchestkit · 82 tokens

stream-chain

Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows.

ruvnet/ruflo · 18 tokens