usernametron/claude-project-structure-assistant/mcp-catalog

MCP Server Catalog

Available Model Context Protocol servers that agents can access when configured in the project's settings.json. This catalog maps user-described capabilities to MCP server names.

Communication & Productivity

Gmail — Read, search, send, and manage emails. Use for agents that need to send notifications, read incoming data from email, or manage communication workflows. User signals: "sends emails", "email notifications", "reads inbox", "email integration" Server name: gmail

Slack — Read channels, post messages, manage threads. Use for agents that need to post updates, read team discussions, or integrate with Slack workflows. User signals: "posts to Slack", "Slack notifications", "team updates", "channel messages" Server name: slack

Google Calendar — Read, create, and manage calendar events. Use for agents that need scheduling awareness or create calendar entries. User signals: "calendar", "scheduling", "meetings", "events" Server name: google-calendar

Development & Deployment

Netlify — Deploy sites, manage builds, configure domains. Use for agents that handle web deployment and hosting. User signals: "deploy to Netlify", "hosting", "publish site", "build and deploy" Server name: netlify

Design & Content

Canva — Create and manage designs, presentations, and visual content. User signals: "create designs", "visual content", "presentations", "graphics" Server name: canva

Data & Research

Indeed — Search jobs, get company data, access resume information. User signals: "job search", "company research", "career data" Server name: indeed

Configuration

To add an MCP server to an agent, include it in the agent's frontmatter:

mcpServers:
  - gmail
  - slack

The server must also be configured in the project's .claude/settings.json or the user's global settings. If a referenced MCP server is not configured, the agent will function without it — MCP access is an enhancement, not a requirement.

Detection Rules for the Concierge

When the user describes their project, map these phrases to MCP recommendations:

"sends emails" OR "email notifications" → suggest Gmail MCP "posts to Slack" OR "team updates" → suggest Slack MCP "deploys to Netlify" OR "hosting on Netlify" → suggest Netlify MCP "calendar integration" OR "scheduling" → suggest Google Calendar MCP

Only suggest MCPs the user has mentioned or implied. Never add MCPs speculatively. If an MCP is suggested but not configured, note the capability gap in the setup summary: "Your deployer could also push to Netlify if you connect it."