Service pack · MCP
MCP Pilot — wire useful QA tools into your assistant
A fixed-scope enablement: wire Assertwise MCP into your team’s editor with scoped access, two or three high-value tools on a real workflow, and a written playbook for secrets, PII and production boundaries.
What’s included
Install, scope, prove
- Discovery: editor (Cursor / Claude / other), target tools (TestHub and/or Accessibility MCP)
- Scoped auth and environment boundaries for a pilot workspace
- 2–3 tools mapped to one real team workflow (not a kitchen-sink tool list)
- Safe-use playbook: what the assistant may call, what stays human-only
- Handover: config notes, known limits, recommended next tools
MCP product access is still early / waitlist. This pack is senior engineering time on enablement — not a promise of a public registry package or SLA uptime.
Who it’s for
Teams that want MCP done right once
QA and platform leads who will not let every engineer paste API keys into chat configs.
- Already using AI editors daily
- Planning TestHub or a11y evidence work
- Need GDPR-oriented wording and clear data boundaries for EU / DACH
Pilot MCP with a senior engineer
Bring your editor setup and one workflow. We’ll say whether Pilot, waitlist-only, or a different pack fits.