Bridge MCP servers to the AGENIUM agent:// network with DNS resolution and mTLS
Stateful agent-to-agent communication client for the agent:// protocol.
AGENIUM provides identity, discovery, and messaging for AI agents. Think of it as DNS + HTTP for agents — each agent gets a unique agent://name URI and can discover and communicate with other agents.
npx @agenium/create-agent my-agent
cd my-agent
npm install
npm start
Choose from 3 templates: echo (hello world), tools (tool-calling), api (REST gateway).
npm install agenium
import { AgeniumClient } from 'agenium';
const client = new AgeniumClient({
apiKey: 'dom_your_api_key_here', // Get one at marketplace.agenium.net
agentUri: 'agent://myagent',
});
// Resolve another agent
const target = await client.resolve('agent://search');
console.log(target.endpoint); // https://...
// Connect and send message
const session = await client.connect('agent://search');
await session.send({ query: 'find MCP servers for GitHub' });
const response = await session.receive();
agent:// Protocol — Unique agent identity via URI schemeagent://name → endpoint)agent://myagent)# Initialize agent configuration
agenium init
# Resolve an agent
agenium resolve agent://search
# Check connection
agenium status
# End-to-end connectivity test
agenium e2e
agent://myagent agent://search
│ │
├── resolve("agent://search") ────►│
│ (DNS lookup via marketplace) │
│◄── endpoint: https://... ───────┤
│ │
├── POST /a2a/message ────────────►│
│ (HTTP/2 + mTLS) │
│◄── response ────────────────────┤
const client = new AgeniumClient({
// Required
apiKey: 'dom_xxx', // Your marketplace API key
agentUri: 'agent://myname', // Your agent URI
// Optional
dnsServer: 'https://marketplace.agenium.net', // DNS resolver
dataDir: './data', // SQLite session storage
timeout: 30000, // Request timeout (ms)
retries: 3, // Max retry attempts
});
client.resolve(agentUri)Resolve an agent URI to its endpoint and capabilities.
client.connect(agentUri)Establish a stateful session with another agent.
session.send(message)Send a message in an active session.
session.receive()Receive the next message in a session.
session.close()Gracefully close a session.
The AGENIUM ecosystem includes:
| Service | URI | Description |
|---|---|---|
| Search | agent://agenium | Agent & tool discovery engine |
| Marketplace | marketplace.agenium.net | Domain registration & credentials |
# Install dependencies
npm install
# Run tests
npm test
# Build
npm run build
# Run E2E tests
npm run e2e
56 tests passing:
MIT
| Package | Description |
|---|---|
agenium | Core client SDK |
@agenium/create-agent | CLI scaffold tool |
@agenium/mcp-server | MCP → agent:// bridge |
discord-agenium | Discord bot gateway |
slack-agenium | Slack app gateway |
n8n-nodes-agenium | n8n automation nodes |
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @agenium/mcp-serverMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-aganium-mcp-server": {
"command": "npx",
"args": [
"-y",
"@agenium/mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@agenium/mcp-servernpmio.github.Aganium/mcp-server works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.