agntcy-mcp-server
MCP bridge for the AGNTCY multi-agent network — agent registry, ACP messaging, SLIM protocol, and capability discovery.
What is AGNTCY?
AGNTCY (Agent Network for Generative and Cognitive Yield) is a Linux Foundation initiative with 65+ enterprise partners (Cisco, Dell, Google, Oracle, Red Hat) for standardized multi-agent communication.
Key protocols:
- ACP (Agent Communication Protocol v1.14): Standard message format for agent-to-agent communication
- SLIM (Secure Low-latency Interactive Messaging): Secure real-time communication with pub-sub and encryption
- AGNTCY Directory: Service registry for agent discovery
Features (7 Tools)
| Tool | Description |
|---|---|
register_agntcy_agent |
Register an agent in the local AGNTCY directory |
discover_by_capability |
Find agents by capability (ranked by relevance) |
create_acp_message |
Create ACP v1.14 compliant messages |
validate_acp_message |
Validate ACP message against spec |
format_slim_message |
Format SLIM secure messages |
get_agntcy_network_info |
AGNTCY ecosystem info (protocols, members, SDKs) |
list_agntcy_agents |
List registered agents with filters |
Installation
pip install agntcy-mcp-server
Usage with Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"agntcy": {
"command": "agntcy-server"
}
}
}
Example Usage
Register an agent:
register_agntcy_agent("DataBot", "Analyzes datasets", ["data-analysis", "summarization"], "https://databot.example.com")
Discover agents by capability:
discover_by_capability("data-analysis")
Create an ACP message:
create_acp_message("agent-1", "agent-2", "Please analyze this dataset", "request")
Format a SLIM message:
format_slim_message("agent-1", "tasks/analysis", "dataset payload", encrypted=True)
Related Servers
- a2a-protocol-mcp-server — Google A2A Protocol bridge
- anp-bridge-mcp-server — Agent Network Protocol (ANP) bridge
- agent-directory-mcp-server — General agent service registry
Links
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for agntcy-mcp-server 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| agntcy_mcp_server-0.1.0.tar.gz | 7.9 kB | Without provenance | Details for agntcy_mcp_server-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agntcy_mcp_server-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for agntcy_mcp_server-0.1.0-py3-none-any.whl |
Total release size: 18.1 kB
Release files / agntcy_mcp_server-0.1.0.tar.gz
| Download URL | agntcy_mcp_server-0.1.0.tar.gz |
|---|---|
| Size | 7.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f0786db757e354e9cec8249bfef103ee7f08f86c4a0ff567003d559dece04a5f
|
|
BLAKE2b-256 checksum How to use checksums |
b5dacee1b9ae1c838d545d4a04660031e9ef2df6079936213be4d5daf780f039
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Release files / agntcy_mcp_server-0.1.0-py3-none-any.whl
| Download URL | agntcy_mcp_server-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
992ae60fe84d51bfb53268d546bb374e400a43fd38cbbec3ae2ec5ea9668793e
|
|
BLAKE2b-256 checksum How to use checksums |
faf3875256f93ad4956b284f006cbb7f1641610d4fce172347c35398bcec45da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Security for agntcy-mcp-server 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
