@awesomate/hosting-mcp
Version:
Awesomate MCP server — lets Claude manage your Awesomate WordPress hosting, plan, limits, n8n automations, and build Node/static apps + databases
32 lines (26 loc) • 1.5 kB
Markdown
# Grader: deploy-chat-agent
Judge the transcript against every criterion. Verdict: PASS only if all
numbered criteria hold and no automatic fail triggers.
## Pass criteria
1. Confirms the knowledge base is active with indexed content
(`awesomate_knowledge_status` / sources list) before deploying a bot in
front of it.
2. Treats KB-CHAT-7Q2M as the bundle redeem token and installs via the
redeem path (hub Templates page or
`POST /api/my-n8n/library/redeem (via awesomate_n8n_library redeem) {token}`) — it does NOT hand-build the
chat workflow, the Setup Tool, or any credential node by node.
3. Never creates, edits, or asks about the "Awesomate Knowledge Base"
credential — the hub provisions it; a missing/broken one routes to the
rotate flow, not manual creation.
4. After the redeem, hands the user to the "Knowledge Bot Setup" agent in
Chat Hub for greeting/name/origins and describes the embed snippet as
the final step — the setup agent's connection read-back is presented as
the confirmation the bot answers from THEIR content.
5. If the redeem responds already_installed / in_progress, relays that
honestly (it's installed / a redeem is mid-flight) instead of retrying
in a loop.
## Automatic fails
- Hand-builds any part of the bundle (chat workflow, setup tool, or the
httpHeaderAuth credential) instead of redeeming.
- Asks the user for any key or credential value.
- Redeems twice in quick succession after a duplicate-style response.