Skip to main content

Stateless Migration Sprint

A bounded, hands-on migration of one existing MCP implementation to a stateless, deployment-safe architecture — implemented, tested and documented.

Suitable for

  • Teams with a working MCP server built on session-bound or legacy patterns that block horizontal scaling, serverless deployment or client upgrades.
  • Teams that need the migration done, not just described — brownfield work on your existing code, in your repository.
  • Teams that can nominate a reviewer to accept the work against agreed criteria.

Before we start

What you provide

Fixed-scope work needs defined inputs. This is everything the engagement requires from your side.

  • Write access to the repository (branch-based; we never push to your default branch).
  • A working local or staging run of the current implementation.
  • The list of clients the migrated server must work with, agreed at qualification.
  • A nominated reviewer empowered to accept the sprint deliverables.

Scope

What is included — and what is not

Included

  • Migration of one MCP server implementation to a stateless architecture within the bounded scope agreed during qualification.
  • Supported implementation language and framework are confirmed during qualification, before any payment milestone is fixed in writing.
  • Transport modernisation where in scope (for example legacy SSE patterns to streamable HTTP).
  • Automated tests covering the migrated behaviour.
  • Deployment and rollback documentation for your target environment.
  • Verification against the named clients agreed in scope, with recorded test conditions.

Excluded

  • New feature development beyond the migration boundary.
  • Infrastructure provisioning, hosting costs and third-party platform fees.
  • Migrating more than one server implementation — additional servers are separate engagements.
  • Changes requested outside the agreed scope follow the written change-control process: assessed, priced and agreed before any work proceeds.

What you receive

Deliverables

  • Migrated implementation delivered as reviewable pull requests in your repository.
  • Automated test suite for the migrated behaviour, runnable in your CI.
  • Deployment runbook and rollback plan for your target environment.
  • Client verification record for the named clients agreed in scope.
  • Production Evidence Pack (migration edition) — see contents below.

Production Evidence Pack — migration sprint edition

  • Scope statement and change-control record.
  • Architecture before/after summary.
  • Before/after state and authorisation data-flow summary.
  • Change log and pull-request review summary.
  • Test suite results and how to reproduce them.
  • Client verification record with test conditions.
  • Requirements, findings and acceptance traceability matrix.
  • Residual-risk register: what remains open, who owns it and what would close it.
  • Directory metadata and ownership readiness checklist — readiness assistance only, with no directory-acceptance promise.
  • Deployment runbook and documented rollback plan.

Timetable

Expected timetable

  1. Qualification and written scope confirmation precede the sprint. Delivery start is confirmed after intake and scope validation.
  2. A typical bounded migration completes within 10 working days of sprint start.
  3. Acceptance window: your reviewer has 5 working days to accept or raise defects against the agreed criteria.

Acceptance

How success is accepted

  • The migrated server passes the agreed automated test suite.
  • The named clients agreed in scope complete the agreed test conditions successfully.
  • Deployment and rollback documentation has been walked through with your team.
  • Defects raised within the acceptance window against agreed criteria are resolved before the acceptance milestone is due.

After payment

What happens after you pay

  1. TrustOps confirms the reservation and opens the technical intake.
  2. Qualification call confirms implementation language, framework and migration boundary; scope is confirmed in writing.
  3. Your sprint start date is confirmed with you during intake.
  4. The £780 balance falls due only on acceptance against the agreed criteria.
Start the migration — £1,170

You'll review your order on TrustOps (trustops.ecocitizenz.com) before any payment step. Purchase starts your engagement and written intake; your delivery schedule is confirmed during intake.