mcp-troubleshooting

mcp-troubleshooting is a skill for Claude Code from mailgun/mailgun-plugins. It costs 30 tokens per session (422 once invoked), scanned A, original, Apache-2.0.

A troubleshooting guide for a Mailgun plugin’s startup, configuration, and missing-tool problems. Mailgun is an email service that can be connected through an MCP server.

In plain words
What is it for?
Debugging Mailgun plugin installation, environment variables, MCP tag filtering, local server overrides, and available-tool checks.
Why use it?
It helps distinguish missing credentials, regional settings, hidden tools, incorrect server versions, and host restart problems without exposing secrets.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the mailgun-claude plugin — 15 skills, 7 commands, 1 MCP server shipped together

Good fit Debugging Mailgun plugin installation, environment variables, MCP tag filtering, local server overrides, and available-tool checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mailgun/mailgun-plugins/mcp-troubleshooting
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.

Any agent
npx skills add mailgun/mailgun-plugins --skill mcp-troubleshooting
Clone the repo
git clone --depth 1 https://github.com/mailgun/mailgun-plugins

Made for: Claude Code.

Or install mailgun-claude, the plugin that ships this one along with the rest of its 15 skills, 7 commands, 1 MCP server.

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-troubleshooting

README.md
[![agentmods](https://agentmods.dev/badge/skills/mailgun/mailgun-plugins/mcp-troubleshooting/github.svg)](https://agentmods.dev/skills/mailgun/mailgun-plugins/mcp-troubleshooting)
Your own site
<a href="https://agentmods.dev/skills/mailgun/mailgun-plugins/mcp-troubleshooting"><img src="https://agentmods.dev/badge/skills/mailgun/mailgun-plugins/mcp-troubleshooting/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.

agentmods 80×15 button for mcp-troubleshooting

Your own site · 80×15
<a href="https://agentmods.dev/skills/mailgun/mailgun-plugins/mcp-troubleshooting"><img src="https://agentmods.dev/badge/skills/mailgun/mailgun-plugins/mcp-troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 422 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.00422
Opus 5.5 $0.00012 $0.00169
Sonnet 5.5 $0.00006 $0.00084
Haiku 4.5 $0.00003 $0.00042

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

Security

Grade A, and why

mcp-troubleshooting 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 1mo 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/mailgun-claude/skills/mcp-troubleshooting/SKILL.md · 34 lines

What it actually says

MCP Troubleshooting

Use this skill when the user is installing a Mailgun plugin, debugging agent startup, checking why tools are missing, testing a local MCP server, or validating environment configuration.

Use Mailgun workflow skills when the MCP server is running and the user wants to perform account tasks.

Intake

Ask for the host app, plugin package, operating system, whether the issue happens at startup or tool call time, and which environment variables are configured. Do not ask the user to paste secrets.

Workflow

  1. Confirm MAILGUN_API_KEY is set in the host environment and that the host was restarted after changes.
  2. Check whether MAILGUN_API_REGION is needed for EU accounts.
  3. Check whether MAILGUN_MCP_TAGS is hiding expected tools. Valid tags are send, validate, optimize, and inspect.
  4. Verify the plugin config launches npx -y @mailgun/[email protected] unless the user is intentionally testing a local server build.
  5. For local testing, point the platform MCP config at the built mailgun-mcp.js from a local mailgun-mcp-server checkout.
  6. Use the MCP Inspector or the host app's tool listing to confirm which Mailgun tools are exposed.
  7. Classify failures as missing environment, wrong region, tag filtering, host reload, local build, network/auth, or account permission issues.

Safety

Never ask users to paste API keys into chat or commit secrets to files. If a config example is needed, use placeholder values such as key-... and explain where the user should set the value locally.

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. 1mo ago Changed a7870d219b4e
  2. 2mo ago First seen · 34 lines · 30 tokens per session scan A e1b3056cd524

Subscribe to this mod's changes

mcp-troubleshooting is a skill published in the GitHub repository mailgun/mailgun-plugins (2 stars, last pushed 15d ago), licensed Apache-2.0. It adds 30 tokens to every session and 422 once invoked, about $0.0001 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-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens

ci-fixer

CI failures - read error, minimal fix, verify.

sipyourdrink-ltd/bernstein · 15 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens

diagnosing-missing-recordings

Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…

PostHog/posthog · 76 tokens