Open Multi-Agent Canvas

Created By
CopilotKita year ago
The open-source multi-agent chat interface that lets you manage multiple agents in one dynamic conversation and add MCP servers for deep research
Overview

What is Open Multi-Agent Canvas?

Open Multi-Agent Canvas is an open-source multi-agent chat interface that allows users to manage multiple agents in a single dynamic conversation, facilitating deep research and various tasks through MCP servers.

How to use Open Multi-Agent Canvas?

To use the Open Multi-Agent Canvas, you need to set up the frontend by installing dependencies, configuring API keys, and running the Next.js project. You can also connect to various MCP-compatible servers for enhanced functionality.

Key features of Open Multi-Agent Canvas?

  • Manage multiple AI agents in one interface.
  • Connect to various MCP servers for diverse functionalities.
  • Built-in MCP Agent for general-purpose tasks.
  • Easy setup with clear documentation.

Use cases of Open Multi-Agent Canvas?

  1. Travel planning with CoAgents Travel Agent.
  2. Conducting AI research with CoAgents AI Researcher.
  3. General-purpose tasks through the MCP Agent.

FAQ from Open Multi-Agent Canvas?

  • Is Open Multi-Agent Canvas free to use?

Yes! It is open-source and free for everyone.

  • What are the prerequisites for using this project?

You need to have pnpm installed and a Copilot Cloud API key.

  • Can I run multiple agents simultaneously?

Yes! You can manage multiple agents in one conversation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
CopilotKit
Star
213
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago