Cohort 01 · August–September 2026

Build one connector.
Ship it clean.

Your mission is to deliver one independent, production-oriented connector with five typed actions, safe authentication, tests, OpenAPI, and a thin MCP adapter.

See the build path Open presentation

builder missions

135

required actions

actions each

shared standard

Independent package

Build once; connect it to WZRD, CNCT, REST, SDKs, or MCP later.

Safe by default

Least privilege, no committed secrets, explicit approval for consequential writes.

Proven in a sandbox

Tests, fixtures, and a real test-account flow without production customer data.

The build path

From assigned mission to deployed MCP

Follow this sequence. Escalate provider-access blockers early instead of hiding them behind mocks.

Understand the provider

Confirm the current API, test account, authentication flow, minimum scopes, rate limits, and access blockers before coding.

Design the five actions

Use the exact assigned action IDs. Define JSON Schema inputs, outputs, examples, and approval requirements for writes.

Build one reusable core

Implement testConnection, listActions, and execute once. Keep provider, auth, schemas, and normalized errors isolated.

Expose a thin MCP adapter

Map the same connector actions to MCP tools. Do not duplicate provider calls or business logic inside the MCP server.

Test, deploy, and validate

Run unit and fixture tests, prove one sandbox flow, deploy an HTTPS MCP endpoint, and submit it to the validation console.

Technical structure

One core. Multiple surfaces.

The connector owns provider logic. MCP is only an adapter that exposes those same actions as tools.

Provider API

Connector core

Thin MCP server

interface DooConnector {
  manifest: ConnectorManifest;
  testConnection(credentials): Promise<ConnectionTestResult>;
  listActions(): ConnectorAction[];
  execute(request): Promise<ConnectorExecutionResult>;
}

Recommended repository

Portable package

connector-name/
├── connector.yaml
├── src/
│   ├── connector.ts
│   ├── client.ts
│   ├── auth/
│   ├── actions/
│   ├── schemas/
│   └── errors/
├── mcp/server.ts
├── tests/
├── fixtures/
├── examples/
├── openapi.yaml
├── .env.example
└── README.md

Mission finder

Find your exact five actions

Search your name, connector, or category. Extra actions are welcome, but these five must work first.

Your assigned connector

Google Sheets

IntermediateProductivity

Builder

Manar Majeed Ahmed Hasan Mohamed

Build these five actions

1sheets.read_range

2sheets.find_rows

3sheets.append_rows

4sheets.update_row

5sheets.create_spreadsheet

Milestones

Build through visible gates

Kickoff

Mission accepted

API/auth research, manifest, five action schemas, repository plan, access risks

First checkpoint

Build continues

Repository, testConnection, mocks, one read action, provider access confirmed or escalated

Week 1 demo

Integration candidate

Working auth, two real actions, normalized errors, tests, initial MCP tools

Final handoff

v1.0.0 ready

All actions, fixtures, OpenAPI, thin MCP server, demo, limitations, versioned release

Evaluation

What earns the score

Working actions and acceptance scenario25%

Authentication and security20%

Connector structure and reusability15%

Schemas and developer experience10%

Reliability, errors, pagination, rate limits10%

Testing and fixtures10%

Documentation and OpenAPI5%

Demonstration and technical explanation5%

Final validation

Deploy it. Then prove it.

The validation console connects to your HTTPS MCP endpoint, discovers tools, matches required actions, checks schemas and safety metadata, and optionally runs sandbox examples.

Open validation console

Deploy

Expose a stable HTTPS MCP URL.

Authenticate

Use a temporary bearer token if needed.

Validate

Run contract, schema, and safety checks.

Review

Share the result slug for review.

Ready to start?

Research first. Build once. Explain everything.

Launch kickoff presentation

Build one connector.Ship it clean.