영어 | 简体中文

서론

Agent Protocol은 OpenJiuwen 생태계 내 에이전트 상호운용성을 위한 프로토콜 SDK와 서비스 레지스트리를 제공합니다. 개발자가 에이전트를 도구와 연결하고, 원격 에이전트와 통신하며, 이용 가능한 서비스를 발견하고, 민감한 작업 전에 검증 가능한 사용자 승인을 강제할 수 있도록 돕습니다.

에이전트 애플리케이션은 단순한 모델과 작업 논리 이상의 것이 필요합니다: 외부 기능에 접근하고, 적합한 협력자를 찾으며, 메시지와 작업 결과를 교환하고, 사용자를 대신해 실행할 수 있는 것을 제한하는 방법이 필요합니다. 이 저장소는 네 가지 보완적인 구성 요소를 통해 이러한 요구를 해결합니다: MCP C++ SDK, A2A C++ SDK, A2X 레지스트리, 그리고 A4P Python SDK. 개발자는 통합 필요에 따라 개별 컴포넌트를 선택하거나 결합할 수 있습니다.

핵심 역량

MCP와의 도구 및 자원 통합

모델 컨텍스트 프로토콜(MCP) C++ SDK는 클라이언트와 서버 기능을 모두 제공하며, 스트림 가능한 HTTP 및 stdio 전송을 지원합니다. 개발자는 MCP 서버를 통해 도구, 리소스, 프롬프트를 노출하거나 기존 MCP 서비스에 연결하는 클라이언트를 구축할 수 있습니다.

Agent Protocol

English | 简体中文

Introduction

Agent Protocol provides protocol SDKs and a service registry for agent interoperability in the openJiuwen ecosystem. It helps developers connect agents to tools, communicate with remote agents, discover available services, route requests across LLM deployments, and enforce verifiable user authorization before sensitive operations.

An agent application needs more than a model and task logic: it needs a way to access external capabilities, locate suitable collaborators, exchange messages and task results, and constrain what it can execute on a user’s behalf. This repository addresses these needs through six complementary components: MCP C++ SDK, A2A C++ SDK, A2X Registry, A4P Python SDK, A4P Java SDK, and IntelliRouter. Developers can choose individual components or combine them according to their integration needs.

Core Capabilities

Tool and resource integration with MCP

The Model Context Protocol (MCP) C++ SDK provides both client and server capabilities, supporting Streamable HTTP and stdio transports. Developers can expose tools, resources, and prompts through an MCP server, or build a client that connects to existing MCP services. The SDK also includes support for authentication, sampling, progress notifications, and roots.

Agent communication with A2A

The Agent2Agent (A2A) C++ SDK implements agent communication over HTTP and JSON-RPC. Clients can discover Agent Cards, send messages, query or cancel tasks, and receive streaming events. Servers can register an AgentExecutor, manage task lifecycles, and expose JSON-RPC endpoints, with extension points such as request interceptors and custom task stores.

Service registration and discovery with A2X

A2X Registry manages agents and services that agents can invoke. It supports registration and deregistration, field-based queries, service-card updates, online/busy/offline states, ownership-based access control, and short-lived reservation leases for Agent Team coordination.

For capability discovery, A2X search combines an automatically constructed hierarchical capability catalog with LLM-guided semantic navigation, allowing agents to locate services from natural-language requests. The registry also provides optional vector search, dataset isolation, HTTP APIs, a Python client, and a web UI for service management and search exploration. A2X search and catalog construction require an LLM configuration; basic registry operations do not.

Verifiable authorization with A4P