US-1240

MCP Server Registry

PLANNED

AI drafted the designLast verified 4 min ago

User story

mcpregistrydiscovery

Channels & integrations · auto-detected from this story

In-app

Acceptance criteria

0 / 2 verified

Each scenario is run as a Playwright test by the QA agent

Scenario 1: List available servers Not run

Giventhe MCP registry

Whena developer queries it

Thenapproved MCP servers are returned with their scopes

Scenario 2: Connect with scoped permissions Not run

Givena selected MCP server

Whenit is connected

Thenonly the granted scopes are exposed to the agent

Spec quality · craft learnings applied

9/10 passing

Generalisable rules the agent applies to every spec — they grow from review feedback & flaky scenarios, and act as a self-improving linter.

Assert one outcome per scenarioAtomicity

Each scenario asserts a single outcome

One trigger per scenarioAtomicity

Every scenario has exactly one trigger

Keep implementation out of Given/When/ThenClarity

Scenarios describe behaviour, not implementation

Make every outcome machine-checkableTestability

Outcomes are concrete and observable

Bound time-sensitive outcomesTestability

Time-sensitive outcomes carry a bound

Pair every happy path with a failure pathCoverage

No failure or edge-case scenario — add the unhappy path

Happy-path-only specs ship bugs; the failure modes are where the real spec lives.

Assert the negative spaceCoverage

At least one scenario asserts the negative

State actor, capability and benefitClarity

Story names actor, capability and benefit

One promise per storyScope

The story makes a single promise

Keep the slice thinScope

2 scenarios — a thin, shippable slice

Learnings applied · from the library

Webhook consumers must be idempotenthigh

External webhook integrations re-deliver; always add a duplicate-delivery scenario and an idempotency decision.

Learned from US-1188 · INC-090 (duplicate charges)

Rate limits are per-tenant, not globalmedium

Limit features should scope quotas per tenant and add a noisy-neighbour scenario.

Learned from support pattern (3 threads)