mcp-integrationlisted

# MCP Integration Skill ## Purpose Wire a repository to MCP servers in a reproducible way: correct scope, credentials kept out of the repo, a bounded tool surface, and documentation a teammate can follow. ## When to use Use this skill when adding an MCP server to a project, auditing an existing configuration, or deciding what belongs in project scope versus a personal setup. ## Inputs - what the integration must let the agent do, stated as tasks not tools - the target service and whether an official MCP server exists - credentials available and how they are currently stored - who else works in this repo and on what platforms ## Output Return: - the server choice with the reason, including why not a plain script or CLI - the configuration, scoped correctly, with credentials referenced by environment variable - the permission entries needed so routine calls do not prompt - a `README` or `CLAUDE.md` section: setup steps, required environment variables, and how to verify it works - a verification run proving the tools respond ## Constraints - prefer the official server for a service over a third-party wrapper; check what it actually exposes before committing to it - **project scope** (`.mcp.json`, committed) for servers everyone on the repo needs; **user scope** for anything personal or credentialed to an individual - never commit tokens, keys, or connection strings — reference environment variables and document which are required - prefer read-only credentials unless a writ