Repository: chintanmehta21/claude-agents
Author: chintanmehta21
Daily Tool Scout Report
Tool 1: Stripe MCP Server
Type: MCP
Source: https://stripe.mcp.run/ (official Stripe vendor server — Streamable HTTP)
Suggested Tag: payments-stripe (new tag — justification: Stripe integration is one of the most common requirements in SaaS/e-commerce apps; a dedicated tag ensures agents always use the official API surface rather than writing raw fetch calls against the Stripe REST API)
Phase: Execution
Use Case: The Stripe MCP exposes customer management, payment links, invoices, subscriptions, balance queries, and dispute handling as first-class tools. Without it, agents hand-roll Stripe calls with a high chance of using deprecated endpoints or missing idempotency keys. With it, every payment-related execution task goes through the officially supported interface, reducing billing bugs and security surface area.
Integration Example: {"name": "stripe", "tools_prefix": "mcp__stripe__", "use_for": "ALL payment operations — customers, subscriptions, invoices, payment links. NEVER call Stripe REST directly.", "mandatory_for": ["payments-stripe"]}
Priority: High
Tool 2: Sentry MCP Server
Type: MCP
Source: https://docs.sentry.io/product/sentry-mcp/ (official Sentry server — cloud at https://mcp.sentry.dev/ or local via npx @sentry/mcp-server)
Suggested Tag: monitoring-sentry (new tag — justification: projects that already have Sentry instrumented should have the pipeline verify error rates and query real issues after deployment, not just check logs manually)
Phase: Both (Execution for wiring up Sentry SDK config; Testing for post-deploy issue inspection)
Use Case: The Sentry MCP provides issue listing, error analysis, Seer AI insights, and project management. In the Testing phase this lets the practical-tester query actual captured errors after a deployment rather than relying solely on Playwright screenshots. In the Execution phase it can verify that the Sentry DSN is correctly set and source maps are configured before shipping.
Integration Example: {"name": "sentry", "tools_prefix": "mcp__sentry__", "use_for": "Query captured errors post-deploy, verify SDK config during execution, analyze issues with Seer insights", "mandatory_for": ["monitoring-sentry"]}
Priority: High
Tool 3: Prisma MCP Server
Type: MCP
Source: https://www.prisma.io/docs/postgres/integrations/mcp-server (built into Prisma CLI v6.6.0+; install via claude mcp add prisma or remote at https://mcp.prisma.io/mcp)
Suggested Tag: database-prisma (new tag — parallel to database-supabase; justification: Prisma is the dominant ORM for Next.js/Node.js backends and needs the same dedicated treatment as Supabase — schema changes and migrations should always go through the MCP, not raw SQL or guessed prisma CLI flags)
Phase: Both (Execution for schema changes and migrations; Testing for verifying migration state and query correctness)
Use Case: The Prisma MCP exposes schema introspection, migrate dev, migrate reset, Prisma Studio access, and query generation. This eliminates the common agent failure mode of writing prisma.schema edits without running migrate dev, or running destructive migrate reset without realizing the consequences. The MCP gates these operations through the official Prisma interface with proper context.
Integration Example: {"name": "prisma", "tools_prefix": "mcp__prisma__", "use_for": "Schema introspection, migrations (migrate-dev, migrate-reset), query generation. ALL schema changes MUST go through this MCP.", "mandatory_for": ["database-prisma"]}
Priority: High
Summary Table
Tool 1: Stripe MCP
Type: MCP
Tag: payments-stripe (new)
Phase: Execution