Repository: chintanmehta21/claude-agents
Author: chintanmehta21
## Daily Tool Scout Report
### Tool 1: Stripe MCP
- **Type**: MCP
- **Source**: https://docs.stripe.com/mcp (`@stripe/mcp`, remote endpoint: https://mcp.stripe.com)
- **Suggested Tag**: `payments-stripe` (new tag — projects that process payments via Stripe)
- **Phase**: Execution + Testing
- **Use Case**: Many SaaS and e-commerce apps use Stripe for billing. The official Stripe MCP lets subagents create/manage customers, products, prices, and invoices directly via the Stripe API — eliminating manual SDK calls and enabling the execution agent to wire up payment flows with live API verification. The testing agent can confirm that customers, subscriptions, and invoice objects were correctly created.
- **Integration Example**:
```json
{"name": "stripe", "tools_prefix": "mcp__stripe__", "use_for": "Customer, product, price, and invoice management via Stripe API", "mandatory_for": ["payments-stripe"]}
```
- **Priority**: High
---
### Tool 2: Sentry MCP
- **Type**: MCP
- **Source**: https://docs.sentry.io/product/sentry-mcp/ (`@sentry/mcp-server`, remote endpoint: https://mcp.sentry.dev/mcp)
- **Suggested Tag**: `monitoring-sentry` (new tag — projects connected to a Sentry org for error tracking)
- **Phase**: Testing
- **Use Case**: After code changes are deployed, new runtime errors can surface silently. The official Sentry MCP lets the testing subagent query open issues, inspect stack traces, and check Seer AI analysis for any regressions introduced by the current execution phase — turning post-deploy monitoring into an active part of the pipeline's quality gate rather than an afterthought.
- **Integration Example**:
```json
{"name": "sentry", "tools_prefix": "mcp__sentry__", "use_for": "Retrieve and analyze error issues, stack traces, and Seer analysis after deployment", "mandatory_for": ["monitoring-sentry"]}
```
- **Priority**: High
---
### Tool 3: Resend MCP
- **Type**: MCP
- **Source**: https://resend.com/mcp (`@resend/mcp`)
- **Suggested Tag**: `email-resend` (new tag — projects that send transactional or marketing emails via Resend)
- **Phase**: Execution + Testing
- **Use Case**: Transactional email (welcome emails, password resets, notifications) is a core requirement in most user-facing apps. The official Resend MCP lets the execution agent send test emails, manage contact lists, configure sender domains, and set up webhooks — all without leaving the pipeline. The testing agent can verify domain DNS records are valid and that email templates render correctly.
- **Integration Example**:
```json
{"name": "resend", "tools_prefix": "mcp__resend__", "use_for": "Send emails, manage contacts, configure domains and webhooks", "mandatory_for": ["email-resend"]}
```
- **Priority**: Medium
---
### Summary Table
| # | Tool | Type | Tag | Phase | Priority |
|---|------|------|-----|-------|----------|
| 1 | Stripe MCP | MCP | `payments-stripe` | Execution + Testing | High |
| 2 | Sentry MCP | MCP | `monitoring-sentry` | Testing | High |
| 3 | Resend MCP | MCP | `email-resend` | Execution + Testing | Medium |
---
### How to Apply
To add these to the pipeline, update:
1. `code_pipeline/skills/lead/SKILL.md` — add new rows to the task tag tables in Phase 3A and 4A
2. `code_pipeline/templates/dependencies.json` — add to `dependencies.mcps` and `phase_assignments.execution.when_tagged` / `phase_assignments.testing_practical.when_tagged`
3. Copy changes to `marketplaces/CM_Agents/plugins/code-pipeline/` (keep in sync)
#### Example additions for `dependencies.json`
```json
{
"name": "stripe",
"required": false,
"purpose": "Payment customer, product, price, and invoice management — mandatory when task is tagged 'payments-stripe'",
"install_method": "mcp-registry",
"registry_keywords": ["stripe", "payments", "billing"],
"tool_prefix": "mcp__stripe__",
"conditional_on_tag": "payments-stripe",
"status": "unknown"
},
{
"name": "sentry",
"required": false,
"purpose": "Error issue retrieval and stack trace analysis — mandatory when task is tagged 'monitoring-sentry'",
"install_method": "mcp-registry",
"registry_keywords": ["sentry", "errors", "monitoring"],
"tool_prefix": "mcp__sentry__",
"conditional_on_tag": "monitoring-sentry",
"status": "unknown"
},
{
"name": "resend",
"required": false,
"purpose": "Transactional email sending, domain configuration, and contact management — mandatory when task is tagged 'email-resend'",
"install_method": "mcp-registry",
"registry_keywords": ["resend", "email", "transactional"],
"tool_prefix": "mcp__resend__",
"conditional_on_tag": "email-resend",
"status": "unknown"
}
```