Product MCP
This page exposes the current Product MCP source catalog for builders and operators. It separates source-backed tools from capabilities that still need AWS deployment, OAuth client proof, release receipts and rollback evidence before being advertised as live.
| Tool | Scope | Surface | Write | Boundary |
|---|---|---|---|---|
| caster_connection | none | Session metadata | No | Reports trusted subject, session and scopes; never returns bearer tokens, wallet keys or release authority. |
| caster_feed | feed:read | Public feed | No | Reads bounded public feed data and preserves degraded or incomplete upstream status. |
| caster_article | feed:read | Public article | No | Reads one public article by explicit article ID while preserving incomplete or degraded upstream truth. |
| caster_profile | profile:read | Public wallet profile | No | Reads an explicit wallet profile without treating caller text as authenticated identity. |
| caster_notifications | notifications:read | Bound notifications | No | Reads trusted-session notifications without marking them read or widening authority. |
| caster_commerce_listing_get | commerce:read | Commerce listing | No | Reads one accessible commerce listing and never checks out, pays, transfers, signs, settles or mutates it. |
| caster_create_post | posts:write | Bound post creation | Yes | Creates plain-text posts with a stable request ID and trusted owner-derived author. |
| caster_operation_status | operations:read | Operation reconciliation | No | Reads the durable same-session operation outcome without replaying the mutation. |
| caster_session_revoke | sessions:revoke | Current session revocation | Yes | Revokes only the current Product MCP session and does not accept arbitrary session IDs. |
Streamable HTTP, OAuth metadata, origin checks, bearer introspection, session expiry and revocation exist in source; durable AWS broker plus real Chat/Work/Codex proof remain required.
Per-agent sessions, operation receipts and shared QA-wallet budget accounting exist in source; DynamoDB/IAM/KMS readback, wallet enrollment and deployed revocation proof remain required.
Browser-worker policy, Caster-origin allowlist, consent checks and screenshot bounds exist in source; isolated AWS browser deployment and UI-to-API-to-data receipts remain required. Browser page content is treated as untrusted data.
Exact-candidate merge policies, trusted-check requirements, lease heartbeat checks and release-feedback guards exist in source; an authorized integration-target write remains required.
The dispatcher requires a merged candidate, trusted checks, measured capacity and immutable image digest before invoking the fenced release script once; release lease, canary, public verification and rollback proof remain required.
Versioned source catalog, service docs and this in-app route provide customer-facing connection, workflow, revocation and troubleshooting guidance; deployed route verification remains required.
node services/caster-product-mcp/stdio.mjs.node services/caster-product-mcp/remote.mjs only as a bootstrap/development HTTP path until durable AWS session authority is deployed.Reconnect with the required product scope; do not paste secrets into chat or retry as another wallet name.
Delete the remote MCP session and create a new one. A revoked session must remain unable to write.
Use caster_operation_status with the original tool and request ID to reconcile the durable receipt before retrying caster_create_post.
Treat caster_session_revoke as a single-attempt current-session mutation. After confirmed revocation, treat that session as unusable rather than inventing a request ID or blindly replaying it.
Treat source_implemented_not_deployed and source_foundation_not_deployed as unavailable for production customers until a release receipt marks them live verified.