RFC: Add MCP-ACP Bridge for Linux Foundation Interoperability

[anivar]

Summary

Add a bridge that exposes MCP tools via ACP REST API with identity configuration support.

Problem

MCP tools cannot be accessed via REST APIs. ACP provides a REST-based protocol but no MCP integration exists.

Solution

Create MCP-to-ACP bridge that:

• Exposes MCP tools as ACP REST endpoints
• Stores identity configuration in manifest metadata
• Provides httpx client support for connection pooling

Implementation (PR #774)

What's Implemented:

• Bridge translates MCP tool calls to ACP REST endpoints
• Identity string stored in manifest metadata
• Custom httpx client support
• Tool discovery and execution

What's NOT Implemented:

• Identity not included in API responses
• No signature verification
• No access control
• Identity is configuration only

Key Features

1. REST API: Access MCP tools via HTTP
2. Tool Discovery: List available MCP tools
3. Stateless Execution: Execute tools via POST
4. httpx Support: Connection pooling and HTTP/2

Future Work

• Add identity headers to requests
• Implement signature verification
• Add access control based on identity

[njbrake]

https://github.com/orgs/i-am-bee/discussions/5