Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
Aganium avatar

Agenium MCP

  • 4 repo stars
  • Updated February 16, 2026
  • Aganium/agenium

AGENIUM MCP is a MCP bridge that connects stdio MCP servers to the AGENIUM agent:// network through DNS discovery.

About

The AGENIUM MCP server is a bridge that links conventional MCP stdio servers into the AGENIUM agent:// ecosystem, using DNS discovery so remote or peer agents can find your tooling. It targets developers experimenting with agent marketplaces, federated assistants, or DNS-resolvable agent endpoints rather than only localhost MCP. Use it in Build when you are wiring agent infrastructure—after you have working MCP tools and want them addressable on the AGENIUM network. Configuration is minimal: npm package plus an optional AGENIUM_DNS_URL override. It matters because discovery is the hard part of multi-agent setups; this server keeps your existing MCP investment and adds network-level reach.

  • AGENIUM MCP bridge v0.1.3 (@agenium/mcp-server) with stdio npm transport.
  • Connects standard MCP servers to the AGENIUM agent:// network using DNS-based discovery.
  • Optional AGENIUM_DNS_URL env var to point at a custom DNS resolver (defaults to public resolver).
  • Monorepo subfolder packages/mcp-bridge on GitHub Aganium/agenium.
  • Lets solo builders publish agent-reachable endpoints without rebuilding MCP from scratch.

Agenium MCP by the numbers

  • Data as of Aug 10, 2026 (Skillselion catalog sync)
terminal
claude mcp add --env AGENIUM_DNS_URL=YOUR_AGENIUM_DNS_URL agenium-mcp-server -- npx -y @agenium/mcp-server

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

Listed on Skillselion
repo stars4
Package@agenium/mcp-server
TransportSTDIO
AuthNone
Last updatedFebruary 16, 2026
RepositoryAganium/agenium

What it does

Expose your local MCP tools to the AGENIUM agent:// network so other agents can discover and reach your server via DNS.

Who is it for?

Advanced developers composing agent networks who already run MCP and want AGENIUM-compatible discovery without rewriting servers.

Skip if: Skip if you only need local Claude Code MCP with no cross-agent DNS publishing, or teams not using AGENIUM.

What you get

After registration, your MCP stack can participate in AGENIUM agent:// resolution so other agents locate your tools via DNS.

  • Running AGENIUM MCP bridge v0.1.3 on stdio
  • DNS-discoverable agent:// exposure for bridged MCP capabilities
  • Optional custom resolver configuration via AGENIUM_DNS_URL

By the numbers

  • Server version 0.1.3 on npm @agenium/mcp-server
  • stdio transport with 1 optional environment variable (AGENIUM_DNS_URL)
  • Repository subfolder packages/mcp-bridge under Aganium/agenium on GitHub
README.md

AGENIUM

Stateful agent-to-agent communication client for the agent:// protocol.

What is AGENIUM?

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.

Quick Start

Create a New Agent (Recommended)

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).

Use as a Library

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();

Features

  • agent:// Protocol — Unique agent identity via URI scheme
  • DNS Resolution — Discover agents by name (agent://name → endpoint)
  • Stateful Sessions — SQLite-backed persistent sessions
  • HTTP/2 + mTLS — Secure transport with mutual TLS
  • At-Least-Once Delivery — Outbox pattern for reliable messaging
  • Circuit Breakers — Automatic failure detection and recovery
  • Prometheus Metrics — Built-in observability

Getting an API Key

  1. Visit marketplace.agenium.net
  2. Register a domain name (e.g., agent://myagent)
  3. Complete purchase (TON payment)
  4. Save your API key (shown only once)

CLI

# Initialize agent configuration
agenium init

# Resolve an agent
agenium resolve agent://search

# Check connection
agenium status

# End-to-end connectivity test
agenium e2e

Architecture

agent://myagent                    agent://search
     │                                  │
     ├── resolve("agent://search") ────►│
     │   (DNS lookup via marketplace)   │
     │◄── endpoint: https://...  ───────┤
     │                                  │
     ├── POST /a2a/message ────────────►│
     │   (HTTP/2 + mTLS)               │
     │◄── response ────────────────────┤

Configuration

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
});

API Reference

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.

Protocol Services

The AGENIUM ecosystem includes:

Service URI Description
Search agent://agenium Agent & tool discovery engine
Marketplace marketplace.agenium.net Domain registration & credentials

Development

# Install dependencies
npm install

# Run tests
npm test

# Build
npm run build

# Run E2E tests
npm run e2e

Tests

56 tests passing:

  • 22 unit tests
  • 24 bug-server integration tests
  • 10 end-to-end tests

License

MIT

Ecosystem

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

Links

Recommended MCP Servers

How it compares

Agent-network MCP bridge, not a payment, browser, or database MCP server.

FAQ

Who is AGENIUM MCP for?

Developers shipping agent-first products who need to bridge existing MCP servers into the AGENIUM agent:// DNS discovery model.

When should I use AGENIUM MCP?

Use it during Build agent-tooling when you want MCP tools reachable on the AGENIUM network, not only on your local stdio session.

How do I add AGENIUM MCP to my agent?

Install @agenium/mcp-server from npm, optionally set AGENIUM_DNS_URL, and register the stdio server in your MCP host alongside the MCP servers you intend to bridge.

AI & LLM Toolsagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.