ACP-MCP-Server

Created By
GongRzhea year ago
A bridge server that connects Agent Communication Protocol (ACP) agents with Model Context Protocol (MCP) clients, enabling seamless integration between ACP-based AI agents and MCP-compatible tools like Claude Desktop.
Overview

What is ACP-MCP-Server?

ACP-MCP-Server is a bridge server that connects Agent Communication Protocol (ACP) agents with Model Context Protocol (MCP) clients, facilitating seamless integration between ACP-based AI agents and MCP-compatible tools like Claude Desktop.

How to use ACP-MCP-Server?

To use ACP-MCP-Server, install it via PyPI and run it with the desired transport mode (STDIO, SSE, or Streamable HTTP) to connect with your ACP agents.

Key features of ACP-MCP-Server?

  • Protocol Bridge: Connects ACP agents with MCP clients.
  • Multiple Transports: Supports STDIO, SSE, and Streamable HTTP.
  • Agent Discovery: Automatically discovers and registers ACP agents.
  • Smart Routing: Routes requests intelligently to appropriate agents.
  • Async Support: Supports both synchronous and asynchronous operations.
  • Interactive Sessions: Enables multi-turn interactions with agents.
  • Multi-Modal: Handles various content types including text and images.

Use cases of ACP-MCP-Server?

  1. Integrating AI agents with desktop applications like Claude Desktop.
  2. Enabling real-time communication between different AI protocols.
  3. Facilitating multi-agent interactions in complex workflows.

FAQ from ACP-MCP-Server?

  • What protocols does ACP-MCP-Server support?

It supports Agent Communication Protocol (ACP) and Model Context Protocol (MCP).

  • Is there a Docker version available?

Yes, you can run ACP-MCP-Server using Docker for easier deployment.

  • What are the system requirements?

You need Python 3.11+ and a running ACP server with agents.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
GongRzhe
Star
0
Language
Python
License
MIT 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
Crevio

2 days ago