AGI-MCP-Agent

Created By
ot2neta year ago
A modular AGI agent framework based on MCP (Multi-Context Processing), inspired by Manus, with ChatGPT-style LLM integration and task control.
Overview

What is AGI-MCP-Agent?

AGI-MCP-Agent is an open-source intelligent agent framework designed to explore and implement advanced agent capabilities through a Master Control Program (MCP) architecture, inspired by Manus, with ChatGPT-style LLM integration and task control.

How to use AGI-MCP-Agent?

To use AGI-MCP-Agent, clone the repository from GitHub, install the necessary dependencies, set up your environment variables, and run the development server using either Poetry or Docker.

Key features of AGI-MCP-Agent?

  • Modular architecture for flexible agent development
  • Integration with various tools and APIs
  • Multi-agent coordination and communication
  • Cognitive processing capabilities including planning and decision-making
  • Environment interface for standardized external interactions

Use cases of AGI-MCP-Agent?

  1. Developing autonomous agents for complex problem-solving
  2. Coordinating multiple agents for collaborative tasks
  3. Experimenting with AI capabilities in research and development

FAQ from AGI-MCP-Agent?

  • Is AGI-MCP-Agent suitable for all types of AI projects?

Yes! It is designed to be flexible and extensible for various AI applications.

  • What programming languages are used in AGI-MCP-Agent?

The backend is primarily developed in Python, with a React frontend.

  • How can I contribute to AGI-MCP-Agent?

Contributions are welcome! Please check the Contributing Guidelines in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ot2net
Star
2
Language
Python
License
MIT license
Tags

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)

14 minutes ago