Feature Request: Support MCP Prompts for GraphQL workflow guidance

[wakita181009]

Problem

Apollo MCP Server supports Tools and Resources but not MCP Prompts. overrides.descriptions works for individual tool guidance, but there's no way to express cross-operation workflows — e.g., "to get a user's order history, call GetUserByEmail → GetUserOrders (cursor-paginated) → GetOrderDetails in sequence."

This kind of orchestration knowledge exists in every GraphQL API but can't be captured in schema descriptions or per-tool overrides alone.

Proposal

Support MCP Prompts via the config YAML:

prompts:
  - name: check_order_history
    description: "Look up a user's recent orders"
    arguments:
      - name: email
        required: true
    messages:
      - role: user
        content: |
          1. GetUserByEmail(email={{email}}) → get userId
          2. GetUserOrders(userId, first=10) → cursor-paginated
          3. GetOrderDetails(orderId) for each order if needed

Context

Claude Code already surfaces MCP Prompts as slash commands (/mcp__server__promptname). Adoption is growing across other clients too. This would complement the existing Tools + Resources support as the third MCP capability.

[DaleSeo]

Thanks for the detailed proposal, @wakita181009! We've tracked this as internally. The workflow orchestration use case you described sounds compelling. We'll follow up here as we make progress.

[wakita181009]

Thanks @DaleSeo. I went ahead and took a stab at implementing this in #706. The PR adds a prompts config section that covers the proposed YAML format. Would love any feedback on the approach!