> ## Documentation Index > Fetch the complete documentation index at: https://docs.chatropic.com/llms.txt > Use this file to discover all available pages before exploring further. # MCP workflows > Ready-to-use prompts for support reviews, content-gap analysis, documentation updates, and billing checks. After [connecting your AI client](https://docs.chatropic.com/user-guides/chatropic-mcp/connect.md), try these prompts in a chat that has the Chatropic tools enabled. Replace the example topic or agent ID with your own. The AI client may ask you to approve tool calls, depending on its settings. ## Review your knowledge coverage **Permissions:** Knowledge reading. > Find our articles about onboarding. Read the relevant articles in full and summarize what is covered, what is missing, and where articles disagree. Include article IDs and distinguish draft content from published content. Do not change anything. The client can search with `search_knowledge` and inspect results with `get_knowledge_article`. Ask it to paginate before claiming it reviewed every article. Articles returned by these tools can be private or disabled for agent use. ## Turn content gaps into a draft plan **Permissions:** Knowledge reading. Add draft editing to create the proposed articles. > Review open content gaps from the last 45 days. Compare them with our existing knowledge, group overlapping gaps, and propose which articles to update or create. Include the supporting gap and article IDs. Wait for my approval before making changes. The client uses `list_knowledge_gaps`, `search_knowledge`, and `get_knowledge_article`. This reads gaps Chatropic has already detected; it does not start a fresh analysis. After reviewing the plan: > Create a private draft for the approved onboarding gap under agent ID AGENT\_ID. Read the documentation-writing guide first, use only the product facts I supplied, and record the source references. Do not publish it. The client can call `get_documentation_skill` and `create_knowledge_draft`. Review the result in Chatropic's Knowledge interface. Creating the article does not automatically mark the originating gap addressed. ## Update an article after a product change **Permissions:** Knowledge reading and draft editing. Add publishing only for the final publishing step. 1. Give your AI client the product change notes or source material it should use. 2. Ask it to compare those facts with existing knowledge. 3. Review its proposed edits before asking it to update the draft. 4. Review the complete updated draft before publishing. Start with: > Our onboarding now includes an optional team invitation step. Compare the change notes I attached with our onboarding articles. Show the exact changes you recommend and flag any facts that need confirmation. Do not edit yet. Then: > Apply the approved changes to ARTICLE\_ID. Retrieve the full draft and current revision first, preserve unrelated sections, and update the draft without publishing. Show me the updated article and revision. The client uses `list_knowledge_drafts` with `article_id` to retrieve complete Markdown and the current revision, then `update_knowledge_draft` to save it. If the revision changed, ask the client to read the article again and reconcile the edits. When the reviewed version is ready: > Publish the article revision I just reviewed. If the revision has changed since my review, stop and show me the new changes first. The client uses `publish_knowledge_article` with the reviewed revision. Publishing does not automatically make a private article public or enable it for an agent. Check its existing Help Center and agent-access settings in Chatropic. ## Investigate a recurring support issue **Permissions:** Conversation reading. Add knowledge reading to compare replies with articles. > Find web support conversations about password resets from the last 30 days. Read the matching conversations and summarize recurring problems and unresolved questions. Cite conversation IDs, note any withheld text, and suggest documentation improvements. Do not send customer replies or edit articles. The client searches with `search_conversations`, then retrieves messages using `get_conversation`. Conversation text is redacted and may be withheld if redaction is unavailable. Ask the AI to identify evidence gaps instead of guessing what missing text says. ## Get a support activity summary **Permissions:** Analytics reading. > Give me the support conversation and resolved counts for the last 30 completed days. Explain the reporting window and identify any suppressed or unavailable values. Do not treat missing counts as zero. The client calls `get_support_metrics`. This provides fixed-window aggregate web support counts, not every metric from the Chatropic analytics dashboard. ## Inspect your agents **Permissions:** Agent configuration reading. > List the agents in this workspace and their IDs. Show the available channel and tool summaries, and clearly label anything missing or withheld. Do not change configuration. The client can use `list_agents` and `get_agent_config`. These return limited summaries based on stored release configuration. Check Builder for the latest saved settings; the MCP tools cannot change them. ## Review billing usage **Permissions:** Billing reading. > Summarize our available plan, seats, usage, remaining credits, and recent invoice summaries. Separate recorded values from unavailable information. Do not make billing changes. The client can call `get_billing_summary`, `get_billing_usage`, and `list_billing_invoices`. Billing-provider differences can affect which values are available. These tools provide information and cannot make purchases or modify your subscription. ## Make results easier to review Ask your AI client to include source IDs, distinguish facts from suggestions, and show the scope of its search. For changes, specify whether you want a proposal, a saved draft, or a published article. A useful instruction for documentation work is: > Read full articles before editing. Preserve unrelated content. Never invent product behavior. Show proposed changes, save drafts only when requested, and publish only the revision I have reviewed. These instructions guide your client; the permissions you grant determine which operations it can actually call. See the [tool reference](https://docs.chatropic.com/user-guides/chatropic-mcp/tools.md) for the complete catalog and limitations. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.