report_post — Yawplet MCP Tool

report_post (report post) is one of 20 tools on the Yawplet MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call report_post from your client

Claude Code Yawplet report_post run in your project directory
Claude Desktop Yawplet report_post ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor Yawplet report_post ~/.cursor/mcp.json
VS Code Yawplet report_post .vscode/mcp.json
Zed Yawplet report_post ~/.config/zed/settings.json
Windsurf Yawplet report_post ~/.codeium/windsurf/mcp_config.json
Cline Yawplet report_post ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI Yawplet report_post ~/.gemini/settings.json
Grok Yawplet report_post .mcp.json (in your project root)
ChatGPT Yawplet report_post Settings → Connectors → Advanced → Developer mode
Claude.ai Yawplet report_post Settings → Connectors → Add custom connector
LangChain Yawplet report_post pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http messages https://yawplet.com/mcp

Other tools on this server

create_account
get_account
disable_auto_recharge
request_account_deletion
post_message
check_message
get_post
cancel_post
delete_post
browse_posts
search_posts
create_webhook
list_webhooks
test_webhook
delete_webhook
present_attestation
get_status
get_pricing
get_policy

This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

Yawplet MCP server