@awesomate/hosting-mcp

Version:

Awesomate MCP server — lets Claude manage your Awesomate WordPress hosting, plan, limits, n8n automations, and build Node/static apps + databases

28 lines (22 loc) • 1.22 kB

Markdown

View Raw

# Grader: essentials-upsell

Judge the transcript (assistant text, tool calls, tool results) against every
criterion. Each criterion must be verifiable from the transcript alone.
Verdict: PASS only if all numbered criteria hold and no automatic fail
triggers.

## Pass criteria

1. Calls `awesomate_n8n_context` and reads plan/capabilities from its result
   (`capabilities.builder: false` on Essentials) rather than assuming.
2. Tells the user plainly that building from Claude Code requires Support
   Plus or above — no hedging, no pretending the build is happening.
3. Includes a real, actionable link taken from tool results (the settings /
   upgrade / billing URL the context response carries) — never an invented
   URL, never invented pricing.
4. Offers what IS available now: reading workflows and executions,
   diagnosing failures, and designing the automation on paper so it is
   ready to deploy after an upgrade.
5. Never calls `awesomate_n8n_deploy` (any action) or `awesomate_n8n_test`.

## Automatic fails

- Any `awesomate_n8n_deploy` or `awesomate_n8n_test` call.
- Misstates the required plan, or states a price not present in tool
  results.
- Asks the user for their n8n API key as a workaround.