Benjamin Taylor
84dd86f2ed
The marked block that wires managed Intelligence is the region a hosted reader copies verbatim, and nothing checked it. Both gaps were deliberate: the parity manifest lists `src/app/api/copilotkit/**` under `allowedDivergence` for every instance it tracks, and no `docker-compose.test.yml` sets `COPILOTKIT_LICENSE_TOKEN`, so every smoke-tested starter takes the else arm and the `intelligence:` arm has never run in CI. The cost was already visible. The block's code was byte-identical in 21 of 22 starters, but its warning comment had drifted into five variants and the two `ms-agent-framework-*` starters shipped the `demo-user` stub with no warning at all. That drift is how the localhost default of OSS-981 survived in all 22 copies at once. Add `scripts/validate-intelligence-wiring-block.ts`, which greps the opening marker, compares every site against the north-star starter, and fails on the first line that differs. Two normalisations keep it usable: the block is dedented, because `agentcore` nests it deeper, and the else arm's runner name is masked, because `agentcore` runs `AgentCoreRunner` in front of a Bedrock session where an in-process runner has nothing to run. Everything else, comment text included, must match to the byte. Then unify the warning at all 22 sites on the fullest wording, which also says the id must exist in Intelligence or thread operations can fail. The check passes on day one, so it is a ratchet rather than a migration. It is a shape gate, not a content gate: 22 identically wrong copies still pass. What it guarantees is that a fix reaches all of them or none. Not covered: enrolling the `intelligence:` arm in the smoke path. That needs a license token in CI and a reachable endpoint from the compose network, and is tracked separately.
CopilotKit <> MCP Apps Starter
This is a starter template for integrating MCP Apps with CopilotKit. It uses the Three.js example from the official Model Context Protocol organization on GitHub.
https://github.com/user-attachments/assets/8908af31-2b64-4426-9c83-c51ab86256de
Project Structure
.
├── app/ # Next.js App Router pages and API routes
│ ├── page.tsx # Main page
│ └── api/copilotkit/ # CopilotKit API route
├── threejs-server/ # MCP App Server (Three.js)
│ ├── server.ts # Server entry point
│ ├── src/ # Three.js app source
│ └── package.json
├── scripts/ # MCP server run scripts
├── next.config.ts
├── tsconfig.json
└── package.json
Prerequisites
Getting Started
- Install dependencies using your preferred package manager:
# Using npm (default)
npm install
# Using pnpm
pnpm install
# Using yarn
yarn install
# Using bun
bun install
The
postinstallscript automatically installs the MCP server dependencies inthreejs-server/.
- Set up your environment variables:
echo 'OPENAI_API_KEY=your-openai-api-key-here' > .env
- Start the development servers:
# Using npm (default)
npm run dev
# Using pnpm
pnpm dev
# Using yarn
yarn dev
# Using bun
bun run dev
This starts both the Next.js app and the MCP server concurrently.
Running a Channel
channel-host.mts mounts the same agent as an Intelligence Channel
(Slack, Teams). It requires INTELLIGENCE_API_KEY and a declared Channel in
.copilotkit/channels.json — set both up with copilotkit init or
copilotkit channels add, which write that file and the credentials your
.env needs, then:
npm run channel
The host reads which Channel to hold from .copilotkit/channels.json. If a
project declares more than one, set INTELLIGENCE_CHANNEL_NAME to pick one.
The host holds no provider credentials and exposes no provider endpoint — Intelligence owns the provider edge — so the same file works for every provider.
The Channel itself is declared in channels.mts — that is where to add commands,
reactions, or an onMention handler. channel-host.mts only owns the process
lifetime, and is byte-identical in every starter.
Once startup finishes, the log reports the truth per Channel:
Channel "<name>" is online.— the session is up and can send.Channel "<name>" is declared but no provider is attached yet.— a normal waiting state, not a failure. Runcopilotkit channels statusto see what setup remains.
Neither message proves the provider app is installed, reachable, or that anyone can message it — verify that separately (invite the bot, then message it) before treating the Channel as working.
Available Scripts
The following scripts can also be run using your preferred package manager:
dev- Starts both the UI and MCP server in development modedev:ui- Starts only the Next.js UI serverdev:mcp- Starts only the MCP App Serverbuild- Builds the Next.js application for productionstart- Starts the production serverchannel- Holds an Intelligence Channel open (see "Running a Channel" above)typecheck:channel- Type-checks the channel host on its owntsconfig.channel.json
Customization
The main UI component is in app/page.tsx. You can:
- Modify the theme colors and styling
- Add new frontend actions
- Customize the CopilotKit sidebar appearance
The MCP App Server code is in threejs-server/.
Documentation
- CopilotKit Documentation - Explore CopilotKit's capabilities
- Next.js Documentation - Learn about Next.js features and API
- MCP Apps Documentation - Learn more about MCP Apps and how to use it
Contributing
Feel free to submit issues and enhancement requests! This starter is designed to be easily extensible.
License
This project is licensed under the MIT License - see the LICENSE file for details.