Intercom Articles MCP Server
Related Servers
Alternatives to Intercom Articles MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server that provides full access to Help Scout's Docs and Inbox APIs. It enables users to manage knowledge base articles, collections, and sites while also handling customer conversations, threads, and mailbox operations.MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP Server implementation that enables managing Confluence wiki pages through natural language queries, supporting operations like creating, updating, deleting, and searching pages across different knowledge bases.2-
- AlicenseNot gradedqualityBmaintenanceMCP server for a content-first knowledge base, enabling AI agents to search (full-text, semantic, hybrid) and retrieve Markdown documents, list content, and find related docs.9 npmMIT
- FlicenseBqualityDmaintenanceEnables management of Product Fruits knowledge base articles, categories, and images through natural language commands via MCP.11-
- AlicenseAqualityDmaintenanceMCP server for managing product documentation as markdown files. Supports creating, reading, updating, deleting, and searching docs with optional semantic search.74 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that exposes Intercom tools to Claude Desktop and sends a daily support report via email.-
TDQS
Scored across 19 tools
Each tool targets a distinct action and resource combination. Conversation tools (add note, close, reply, get, search) are clearly differentiated from article and collection CRUD, tickets, admins, and email. No ambiguity.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_article, list_collections, search_conversations). No mixed conventions or irregular names.
19 tools cover articles, collections, conversations, tickets, admins, and outbound email. While slightly high for a single server, the scope justifies the count, and each tool has a clear role.
Articles and collections have full CRUD, but conversations lack update and delete operations, tickets only have state update, and there is no search for collections. Notable gaps exist in the conversation and ticket lifecycle.