Implement the server and tools

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Implement the MCP server. Register each tool with its schema and description; implement handlers that validate inputs server-side (even though schemas exist - defense in depth), execute the real logic, and return results as proper MCP content; convert every handler exception into a structured tool error result (never let it crash the transport); add logging of every call: tool, arguments, duration, result size or error. Choose the transport per my deployment: stdio for local host integration, HTTP/SSE-style for remote per current spec guidance. Start the server and confirm it initializes cleanly.

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A running server with validated, logged, error-safe tools.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Handlers validate independently of schemaExceptions become error resultsEvery call logged with duration

Do not continue if…

! Hand-rolled protocol handling that breaks on the first spec nuance
! Tools that work in isolation but fail through the host's serialization
! Errors thrown as exceptions that kill the server instead of error results
! No logging, making host-side failures undiagnosable

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

The server dies on a handler exception. Wrap handler dispatch in a top-level try/except that returns an MCP error result - the transport must survive any tool failure.