feat(search-mcp): persist client-attributed tool activity

[waleedlatif1]

Summary

• Persist content-free Search MCP tool activity with OAuth client attribution, outcome, duration, and organization scope.
• Record activity after the response with a bounded database write, and snapshot client names for future usage reporting.
• Preserve authenticated client attribution in JSON and OpenTelemetry logs.

Type of Change

• New feature

Testing

Focused MCP/auth tests and logger tests passed, along with the real PostgreSQL/MCP integration suite. Verified the full migration chain and an idempotent second run against a disposable database. Type checks, lint, all repository audits, API boundary validation, and migration safety checks passed.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 16, 2026 8:58pm UTC

[cubic-dev-ai]

All reported issues were addressed across 12 files

<sub>Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.

Fix all with cubic | Re-trigger cubic</sub>

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; the previous cancellation issue is resolved and no new actionable defects remain.

Summary

This PR adds content-free, organization-scoped persistence for Search MCP tool activity and carries authenticated OAuth client attribution into activity and operational logs.

• Records tool name, outcome, duration, organization, optional user, authentication kind, and an admission-time OAuth client-name snapshot after the response.
• Adds the corresponding Drizzle schema, SQL migration, constraints, indexes, and schema mocks.
• Keeps OAuth display metadata out of serialized workflow authority while propagating authenticated client IDs through JSON and OpenTelemetry logs.
• Covers successful, erroneous, rate-limited, and cancelled tool calls, including cancellation around rate-limit admission.

Diagram

sequenceDiagram
  participant Client as MCP Client
  participant Auth as OAuth/API-key Auth
  participant MCP as Search MCP Server
  participant Tool as Search Tool
  participant Log as Operational Logs
  participant DB as Activity Store

  Client->>Auth: Authenticated tool request
  Auth-->>MCP: Verified principal and organization scope
  MCP->>MCP: Check cancellation
  MCP->>MCP: Enforce rate limit
  alt Admitted
    MCP->>Tool: Execute with combined abort signal
    Tool-->>MCP: Result or error
  else Rate limited or cancelled
    MCP->>MCP: Produce tool error
  end
  MCP->>Log: Emit content-free completion metadata
  MCP-->>Client: Tool response
  MCP-->>DB: After response, persist attributed activity

Loading

_{Reviews (2) · Last reviewed commit: "fix(search-mcp): snapshot client attribu..."}

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 16 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.

Re-trigger cubic</sub>