copilotkit__copilotkit/examples/integrations/mastra

CopilotKit <> Mastra Starter

This is a starter template for building AI agents using Mastra and CopilotKit. It provides a modern Next.js application with integrated AI capabilities and a beautiful UI.

Prerequisites

• Node.js 18+
• Any of the following package managers:
  • npm (default)
  • pnpm
  • yarn
  • bun

Getting Started

1. Add your OpenAI API key

# you can use whatever model Mastra supports
echo "OPENAI_API_KEY=your-key-here" >> .env

2. Install dependencies using your preferred package manager:

# Using npm (default)
npm install

# Using pnpm
pnpm install

# Using yarn
yarn install

# Using bun
bun install

3. Start the development server:

# Using npm (default)
npm run dev

# Using pnpm
pnpm dev

# Using yarn
yarn dev

# Using bun
bun run dev

This will start both the UI and agent servers concurrently.

Running a Channel

channel-host.mts mounts the same agent as an Intelligence Channel (Slack, Teams). It requires CPK_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. Run copilotkit channels status to 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.

Unlike the other starters, this one has no typecheck:channel script: the host's import chain reaches src/mastra/**, which carries a pre-existing type error unrelated to the Channel host (see the comment in tsconfig.channel.json).

Available Scripts

The following scripts can also be run using your preferred package manager:

• dev - Starts both UI and agent servers in development mode
• dev:ui - Starts only the Next.js UI server
• dev:agent - Starts only the Mastra agent server
• dev:debug - Starts development servers with debug logging enabled
• build - Builds the application for production
• start - Starts the production server
• channel - Holds an Intelligence Channel open (see "Running a Channel" above)

Documentation

• Mastra Documentation - Learn more about Mastra and its features
• CopilotKit Documentation - Explore CopilotKit's capabilities
• Next.js Documentation - Learn about Next.js features and API

Contributing

Feel free to submit issues and enhancement requests!

License

This project is licensed under the MIT License - see the LICENSE file for details.

CopilotKit Intelligence & Threads (Optional)

CopilotKit Intelligence adds durable thread history and cross-session memory to your agent. It requires a COPILOTKIT_LICENSE_TOKEN, a CPK_INTELLIGENCE_API_KEY, and a running local Intelligence stack (Docker Desktop + a local Intelligence repo checkout).

Prerequisites

• Docker Desktop running
• A COPILOTKIT_LICENSE_TOKEN (obtain from CopilotKit Cloud)
• A CPK_INTELLIGENCE_API_KEY for the Intelligence project
• The Intelligence repo cloned locally. The docker-compose.intelligence.yml defaults to a sibling directory at ../../../Intelligence relative to this starter; override with the INTELLIGENCE_REPO env var if your checkout is elsewhere.

Start the intelligence stack

# From inside this starter directory:
docker compose -f docker-compose.intelligence.yml up -d --wait

First run builds the intelligence image from source (may take several minutes).

Verify the stack is healthy

docker compose -f docker-compose.intelligence.yml ps

All three services (postgres, redis, intelligence) should show healthy.

Set environment variables

Add the following to your .env file:

COPILOTKIT_LICENSE_TOKEN=your-license-token-here
CPK_INTELLIGENCE_API_KEY=your-project-api-key-here
INTELLIGENCE_API_URL=http://localhost:4204
INTELLIGENCE_GATEWAY_WS_URL=ws://localhost:4404

Then start the dev server as usual (npm run dev). Thread history and memory features are activated automatically when CPK_INTELLIGENCE_API_KEY is set.

Stop / reset

# Stop without removing data:
docker compose -f docker-compose.intelligence.yml down

# Full reset (removes postgres + redis volumes):
docker compose -f docker-compose.intelligence.yml down -v