mcp-integration-reference

# MCP Integration Reference Pattern > This is a template skill. It shows how to structure a skill that wraps an MCP server. Replace `sentry` with your MCP server name and adapt the reference file at `references/sentry-mcp.md`. ## What This Pattern Solves When a skill calls an MCP server without prior context, Claude guesses at the query syntax. This works for simple calls but breaks on anything with non-obvious behavior: pagination quirks, required parameter combinations, rate limits, or subtle format restrictions. The fix: a `references/<mcp-name>.md` file that captures all the gotchas. The skill reads this file before making any MCP call. Zero guessing. Three types of content go in the reference file: 1. Parameter semantics that differ from what the tool name implies 2. Known error patterns and their root causes 3. Working query examples (copy-paste, no thinking required) --- ## Step 1: Read the MCP Reference File **Before doing anything else**, read the full MCP reference: ``` Read: references/sentry-mcp.md ``` This file contains query syntax, known gotchas, and working examples for the Sentry MCP. Do not skip this step. --- ## Step 2: Gather Scope from User Ask the user: - **Time range**: Last 24h? 7 days? Custom range? - **Environments**: `production`, `staging`, or both? - **Projects**: All projects or specific ones? (Default: all) If the user says "just run it with defaults", use: - Time range: last 72 hours - Environment: `production` only - Projects: a...