could-have-been-email 1 tool

MCP server exposing 1 tool for could-have-been-email.

Endpoint

This URL is a JSON-RPC 2.0 endpoint over HTTP. Issue POST requests with a JSON-RPC body. Browsers and search crawlers land here on GET.

POST https://gateway.pipeworx.io/could-have-been-email/mcp
Content-Type: application/json

{"jsonrpc":"2.0","id":1,"method":"tools/list"}

Tools

• could_have_been_email_analyze — Check if a meeting transcript could have been an email instead. Returns filler word count, decisions made, action items, and a suggested email that would've replaced the meeting.

Full documentation

Code samples (curl / TypeScript / one-click client install), schemas, and the live playground are on the pack page:
https://pipeworx.io/packs/could-have-been-email/

About Pipeworx

Pipeworx is an open MCP gateway connecting AI agents to live data. pipeworx.io