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.
npx skills add sshh12/claude-plugins --skill diy-mcp-connectorgit clone --depth 1 https://github.com/sshh12/claude-pluginsWrote 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.
[](https://agentmods.dev/skills/sshh12/claude-plugins/diy-mcp-connector)<a href="https://agentmods.dev/skills/sshh12/claude-plugins/diy-mcp-connector"><img src="https://agentmods.dev/badge/skills/sshh12/claude-plugins/diy-mcp-connector/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.
<a href="https://agentmods.dev/skills/sshh12/claude-plugins/diy-mcp-connector"><img src="https://agentmods.dev/badge/skills/sshh12/claude-plugins/diy-mcp-connector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00066 | $0.03124 |
| Opus 5 | $0.00033 | $0.01562 |
| Sonnet 5 | $0.00013 | $0.00625 |
| Haiku 4.5 | $0.00007 | $0.00312 |
Grade A, and why
diy-mcp-connector 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This skill runs in Claude Code and builds a standalone MCP server that turns one web app's API into purpose-built tools. The connector you build works with Claude Code, Claude Desktop (Cowork), and any other MCP-supporting application. The result is a Node.js server that handles authentication, response formatting, and tool routing — one dedicated server per app.
All 9 stages are mandatory. Complete each in order — do not skip ahead. Each stage has a gate condition that must be met before proceeding.
Stages can loop. Auth or API issues discovered in Stages 6-7 may require returning to Stage 2 to reclassify the app type, then re-running Stages 5-7. This is expected — the linear numbering is the happy path, not a one-way gate.
Prerequisites
- Node.js 18+ and npm
- Python 3 (for HAR analysis script)
- Google Chrome (for auto-login via CDP)
@modelcontextprotocol/sdknpm package (installed during build)- Optional (for live exploration): Claude for Chrome, brw, Playwright MCP, or Chrome DevTools MCP — any browser MCP server enables live API discovery instead of manual HAR capture
Getting Started
- Ask the user which web app they want to connect
- Detect available browser tools (
claude mcp list) — seereferences/1-capture-api.mdfor the detection table and preference order - If no browser tools found, ask if they have HAR files or want to set up a browser tool (Claude for Chrome is the easiest)
- Create the project directory:
<app>/ - Copy the analyze script:
cp "${SKILL_DIR}/scripts/analyze-har.py" <app>/scripts/
Stage 1: Capture API Surface
See references/1-capture-api.md
- If api-key-auth with documented API: skip HAR, document endpoints from docs/existing code
- Otherwise: detect available browser tools via
claude mcp list - Choose capture method: HAR files, live exploration (using detected tool), or both
- Capture API traffic across all major app sections (not just one page)
- Save HAR to
<app>/har/<app>.har(if using HAR method)
What ships with it
21 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/1-capture-api.md 7.8 KB
- references/10-challenges-feedback.md 3.6 KB
- references/2-analyze-api.md 9.5 KB
- references/3-design-tools.md 12 KB
- references/4-security-review.md 5.9 KB
- references/5-build.md 15 KB
- references/6-auth-verification.md 5.2 KB
- references/7-test.md 3.3 KB
- references/8-optimize.md 3.8 KB
- references/9-package-connect.md 8.3 KB
- references/patterns/api-key-auth.md 2.9 KB
- references/patterns/graphql-allowlist.md 4.3 KB
- references/patterns/sdui.md 3.8 KB
- references/patterns/spa-token-auth.md 5.1 KB
- scripts/analyze-har.py 12 KB runs code
- scripts/auth.js 18 KB runs code
- scripts/csrf.js 2.8 KB runs code
- scripts/graphql.js 1.8 KB runs code
- scripts/output.js 5.6 KB runs code
- scripts/server.js 4.3 KB runs code
- scripts/test-tool.sh 3.8 KB runs code
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.
- 10d ago First seen · 248 lines · 66 tokens per session scan A 5a981f5e2762
diy-mcp-connector is a skill published in the GitHub repository sshh12/claude-plugins (22 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 3,124 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.
Other skills, from other repositories
frontmcp-development
Use when building any FrontMCP server component other than a tool (for tools, use create-tool). Covers @Resource static resources and parameterized URI templates; @Prompt reusable prompts (RAG, multi-turn); @Provider singleton dependency-injection providers (database pools, API clients); @Agent autonomous LLM agents…
pipefy-api-fallback
Use this skill when an MCP tool fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow the 3-tier…
pipefy-introspection
Use this skill when you need to discover GraphQL type shapes, mutation signatures, enum values, or execute arbitrary GraphQL as a fallback. This is the first fallback tier (Tier 2) when dedicated MCP tools fail or don't exist for an operation. 7 MCP tools.
pipefy-ipaas
Use when the user wants to build, test, publish, or manage iPaaS (Advanced Automations) flows: multi-step integrations with external apps (Slack, Gmail, Google Sheets), incoming webhooks, schedules, routers, code steps, or iPaaS data tables. MCP-only, driven through 4 meta-tools over a per-pipe catalog discovered at…
pipefy-members-email-webhooks
Use this skill when the user wants to manage pipe membership, send or read card inbox emails, use email templates, or manage webhooks. Covers 12 MCP tools.
api-designer
Design RESTful APIs with best practices for consistency and usability.