Repository navigation
v0.8.2 — conversation read tools + slim responses
What's new
Adds two read tools and slims every action-tool response so long conversations no longer flood the MCP client's context.
New tools
search_conversations— search by raw Intercom query object, paginated (per_page/starting_after); returns a slim list (id/state/contact/timestamps, no parts). Accepts the query object even when a client serializes it as a JSON string.get_conversation— full message history, slimmed: system-event parts filtered out, triage essentials kept (sourceincl.delivered_as, ticket-formticket_attributes,contacts), each part flaggedfrom_quick_reply(distinguishes a typed reply from a tapped quick-reply option), plustotal_parts/included_parts.
Slimmed responses
reply_conversation / close_conversation / add_conversation_note / create_article / update_article / update_ticket_state now return a small confirmation object instead of the full Intercom payload. get_article / delete_article / collection tools unchanged.
Impact (verified on a 57-part conversation): a reply that previously returned ~70K chars now returns 6 fields; get_conversation 41.6K → ~13K (63% smaller).
Rolls up v0.8.0 (new tools + slim action responses), v0.8.1 (query-as-string fix), v0.8.2 (restore triage-essential fields in get_conversation).
🤖 Generated with Claude Code