sync: packages/mcp @ f3197677a514ba393d17f7ed5b3e7967270cde2a

Author: dynamoi-bot

docs/engineers.md

@@ -51,7 +51,7 @@ Private implementation (not published):
 
 ## Monitoring MCP UX (No Dashboard Needed)
 
-We intentionally rely on structured logs + Sentry so audits stay simple and reproducible.
+We rely on structured error-level logs and Axiom so audits stay simple and reproducible.
 
 ### Log Surfaces
 
@@ -76,10 +76,10 @@ We intentionally rely on structured logs + Sentry so audits stay simple and repr
 Use the copy/paste queries in:
 - `.agents/skills/querying-data/references/observability-queries.md` → **MCP Server UX Audit (Axiom)**
 
-### Sentry Behavior
+### Error Logging Behavior
 
-- Validation/business failures remain warning-level (not Sentry noise).
-- Platform/unknown failures continue through error-level logging and are sent to Sentry with enriched MCP context (client/tool/user/timing).
+- Validation/business failures remain warning-level.
+- Platform/unknown failures continue through error-level structured logs with enriched MCP context (client/tool/user/timing).
 
 ## Adding Or Modifying A Tool (Safe Checklist)
 

docs/research.md

@@ -55,7 +55,7 @@ MCP (Model Context Protocol) is the de facto standard for AI agent-to-tool conne
 - 97M+ SDK downloads
 - Donated to Linux Foundation's AAIF (Dec 2025)
 - Adopted by every major AI company: Anthropic, OpenAI, Google, Microsoft
-- Companies shipping MCP servers: Stripe (25 tools), Notion (16 tools), Sentry (~16 tools), Figma, Cloudflare, Linear, Intercom
+- Companies shipping MCP servers: Stripe (25 tools), Notion (16 tools), Figma, Cloudflare, Linear, Intercom
 
 ### Other Protocols (Less Relevant)
 
@@ -121,10 +121,6 @@ The MCP server package only. Tools, auth middleware, transport layer. No busines
 - `search_stripe_resources` cross-cutting search is powerful pattern
 - `search_stripe_documentation` searches their own docs
 
-**Sentry:**
-- "Intentionally consolidated rather than bloated with single-purpose functions"
-- Search-oriented tools that return rich context
-
 **Community Meta Ads MCP (29 tools):**
 - 1:1 API mapping. What NOT to do -- Dynamoi already handles Meta complexity internally
 
@@ -261,7 +257,7 @@ The same role resolution functions from `apps/main/app/lib/domains/artist/access
 
 ### API Keys vs OAuth
 
-Industry pattern (Stripe, Notion, Sentry): **support both**.
+Industry pattern (Stripe, Notion): **support both**.
 
 | Transport | Auth Method |
 |---|---|
@@ -688,8 +684,6 @@ This flips the funnel. Instead of SEO → landing page → signup → learn dash
 - [Stripe MCP Docs](https://docs.stripe.com/mcp)
 - [Notion MCP Tools](https://developers.notion.com/docs/mcp-supported-tools)
 - [Notion Hosted MCP: Inside Look](https://www.notion.com/blog/notions-hosted-mcp-server-an-inside-look)
-- [Sentry MCP Server](https://docs.sentry.io/product/sentry-mcp/)
-- [Sentry MCP GitHub](https://github.com/getsentry/sentry-mcp)
 - [Meta Ads MCP (Pipeboard)](https://github.com/pipeboard-co/meta-ads-mcp)
 - [Google Ads MCP](https://github.com/cohnen/mcp-google-ads)
 - [MCP "Too Many Tools" Problem](https://demiliani.com/2025/09/04/model-context-protocol-and-the-too-many-tools-problem/)

docs/spec.md

@@ -723,7 +723,7 @@ Annotations:
 **Error classification:**
 - `ValidationError` → return Result error with user message, kind: "validation"
 - `BusinessRuleError` → return Result error with user message, kind: "business"
-- `PlatformFailureError` → return Result error with actionable message, kind: "platform", log to Sentry
+- `PlatformFailureError` → return Result error with actionable message, kind: "platform", log at error level
 
 #### `dynamoi_resume_campaign`
 
@@ -1313,7 +1313,7 @@ Minimal UI components:
 - Rate limiting (best-effort in-memory at `/mcp`)
 - Circuit breaker/backoff for Meta/Google mutations (MCP-only)
 - Audit logging (integrate with `domains/audit`) including campaign creation
-- Sentry logging for `PlatformFailureError` + unknown only (validation/business warn-only)
+- Error-level structured logging for `PlatformFailureError` + unknown only (validation/business warn-only)
 - **Connected Apps revocation page** (`/settings/connected-apps` redirects to `/<locale>/settings/connected-apps`) — list authorized clients, revoke grants
 - Server instructions + prompts (dynamic resources already implemented)
 - Load testing
@@ -1495,7 +1495,7 @@ Then a realistic workflow:
 - Rate limit:
   - Rapid tool calls should trigger `429` with `Retry-After`.
 - Platform failure classification:
-  - When Meta/Google rejects a mutation, tool should return error kind: `platform` (and log to Sentry).
+  - When Meta/Google rejects a mutation, tool should return error kind: `platform` and emit error-level logs.
 - Circuit breaker:
   - Repeated platform failures should temporarily block and return a retry-after style message.
 - Margin leakage:
@@ -1604,9 +1604,9 @@ Token → resolveUserFromToken() → User (AUTHENTICATED | SUPER_ADMIN)
 ### Error Classification
 
 ```
-ValidationError      → user input error, return message, kind: "validation", no Sentry
-BusinessRuleError    → business logic violation, return message, kind: "business", no Sentry
-PlatformFailureError → Meta/Google API rejection, return actionable message, kind: "platform", log to Sentry
+ValidationError      → user input error, return message, kind: "validation", warning-level only
+BusinessRuleError    → business logic violation, return message, kind: "business", warning-level only
+PlatformFailureError → Meta/Google API rejection, return actionable message, kind: "platform", log at error level
 ```
 
 ### Onboarding Requirements