AgentMCP: Multi-Agent Collaboration Platform

Created By
geniusgeeka year ago
MCPAgent for Multi-agent Collaboration Network (MACNET) with Model Context Protocol (MCP) capabilities baked in
Overview

What is AgentMCP?

AgentMCP is a Multi-Agent Collaboration Platform that utilizes the Model Context Protocol (MCP) to facilitate seamless collaboration among AI agents. It allows developers to easily integrate their agents into a global network with just one line of code.

How to use AgentMCP?

To use AgentMCP, install the package via pip, import the mcp_agent decorator, and decorate your agent class with @mcp_agent. This instantly connects your agent to the Multi-agent Collaboration Network (MCN).

Key features of AgentMCP?

  • One-line integration to transform any agent into an MCP agent.
  • Automatic network registration for agents.
  • Framework agnostic, compatible with various AI frameworks.
  • Built-in adapters for popular frameworks like Langchain and CrewAI.

Use cases of AgentMCP?

  1. Enabling collaboration between specialized AI agents for complex tasks.
  2. Facilitating real-time communication and context sharing among agents.
  3. Allowing developers to create custom agents that can interact within a global network.

FAQ from AgentMCP?

  • Can I use AgentMCP with any AI framework?

Yes! AgentMCP is designed to work with any AI framework or custom implementation.

  • How do I register my agent?

Simply decorate your agent class with @mcp_agent, and it will automatically register with the network.

  • Is there any setup required?

No complex setup is needed; just install the package and use the decorator.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
geniusgeek
Star
3
Language
Python
License
-

Recommend Servers

View All
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