Agenium Mcp Server

io.github.chorghemaruti64-creatorPublished by GitHub account chorghemaruti64-creatorv0.1.3Updated Oct 24, 2026

Bridge MCP servers to the AGENIUM agent:// network via DNS discovery

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

A local npm library that bridges MCP servers onto the AGENIUM agent:// network, registering them on AGENIUM DNS so other agents can discover and call their MCP.

What you can do
Expose an MCP server as an AGENIUM agent: spawn a stdio MCP server or connect to an SSE or streamable-HTTP one, then register it on AGENIUM DNS under an agent:// name and list its tools, resources and prompts. Call tools on remote bridged agents: discover an agent's tools and invoke a named tool with arguments. Serve the agent:// protocol methods for listing and calling tools, reading resources, fetching prompts, capability manifests and health checks. Emit bridge events for readiness, registration, tool calls, results, errors and shutdown.
When to use it
Use it when you want to publish an existing MCP server as a discoverable, callable agent on the AGENIUM network, or when an agent needs to discover and call tools on remote AGENIUM-bridged MCP servers.
Requirements
Node.js with the npm package @agenium/mcp-server, run as a local process. An MCP server to bridge (stdio command, SSE URL or streamable-HTTP URL). Network access to AGENIUM DNS, by default the public resolver, overridable with AGENIUM_DNS_URL or the dnsServer option. A public host/IP for registration.
Before you install
Bridging registers the server on a public DNS resolver and exposes its tools, resources and prompts to other AGENIUM agents, so anything reachable through the bridged MCP server becomes callable remotely. Remote tool calls can act on your data. The default DNS resolver is a third-party address; point AGENIUM_DNS_URL at a resolver you trust if needed.

Installation

In SourceWeft

  1. Open Agenium Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@agenium/mcp-server

Bridge MCP (Model Context Protocol) servers to the AGENIUM agent:// network.

Any MCP server → discoverable, callable agent on the AGENIUM network.

Install

bash
npm install @agenium/mcp-server

Quick Start

Expose an MCP server as an AGENIUM agent

typescript
import { MCPBridge } from '@agenium/mcp-server';
const bridge = new MCPBridge({  name: 'weather-tools',  mcp: {    transport: 'stdio',    command: 'npx',    args: ['-y', '@modelcontextprotocol/server-weather'],  },  agent: {    publicHost: '203.0.113.1', // Your server's public IP  },});
await bridge.start();// ✅ MCP server connected// ✅ Found 2 tools: get_forecast, get_alerts// ✅ AGENIUM agent "weather-tools" started// ✅ Registered on AGENIUM DNS as agent://weather-tools
console.log(bridge.getTools());// [{ name: 'get_forecast', description: '...', inputSchema: {...} }, ...]

Call tools on a remote MCP-bridged agent

typescript
import { MCPAgentClient } from '@agenium/mcp-server';
const client = new MCPAgentClient('my-agent');await client.start();
// Discover what tools an agent hasconst info = await client.discover('agent://weather-tools');console.log(info.tools);
// Call a toolconst result = await client.callTool('agent://weather-tools', 'get_forecast', {  city: 'Tehran',  days: 3,});console.log(result.content);
await client.stop();

Configuration

MCPBridgeConfig

typescript
{  // Agent name on the AGENIUM network  name: string;
  // MCP server configuration  mcp: {    // stdio: spawn a child process    transport: 'stdio';    command: string;    args?: string[];    cwd?: string;    env?: Record<string, string>;  } | {    // SSE: connect to running server    transport: 'sse';    url: string;    headers?: Record<string, string>;  } | {    // Streamable HTTP (MCP v2)    transport: 'streamable-http';    url: string;    headers?: Record<string, string>;  };
  // AGENIUM agent options  agent?: {    port?: number;           // Listen port (default: auto)    dnsServer?: string;      // DNS server (default: 185.204.169.26)    dnsPort?: number;        // DNS port (default: 3000)    autoRegister?: boolean;  // Register on DNS (default: true)    publicHost?: string;     // Public IP for registration    dataDir?: string;        // State directory  };
  // Bridge behavior  bridge?: {    toolCallTimeoutMs?: number;  // Tool call timeout (default: 30s)    exposeResources?: boolean;   // Expose MCP resources (default: true)    exposePrompts?: boolean;     // Expose MCP prompts (default: true)    logLevel?: 'debug' | 'info' | 'warn' | 'error' | 'silent';  };}

Protocol

When an MCP server is bridged, it exposes these agent:// request methods:

MethodDescriptionParams
tools/listList available tools—
tools/callCall a tool{ name, arguments? }
resources/listList available resources—
resources/readRead a resource{ uri }
prompts/listList available prompts—
prompts/getGet a prompt{ name, arguments? }
capabilitiesGet full capability manifest—
pingHealth check—

Events

typescript
bridge.on('ready', ({ tools, resources, prompts }) => { ... });bridge.on('registered', ({ name, endpoint }) => { ... });bridge.on('tool:call', ({ tool, sessionId }) => { ... });bridge.on('tool:result', ({ tool, sessionId, durationMs }) => { ... });bridge.on('tool:error', ({ tool, sessionId, error }) => { ... });bridge.on('error', (err) => { ... });bridge.on('stopped', () => { ... });

How It Works

┌─────────────┐     agent://      ┌──────────────┐     JSON-RPC      ┌────────────┐│ Agent Client │ ──────────────▶  │  MCP Bridge   │ ──────────────▶  │ MCP Server ││              │                  │  (@agenium/   │                  │ (any tool) ││ Any AGENIUM  │  ◀──────────────  │  mcp-server)  │  ◀──────────────  │            ││ agent        │     response     │               │    tool result   │            │└─────────────┘                  └──────────────┘                  └────────────┘                                       │                                       │ registers                                       ▼                                 ┌──────────────┐                                 │ AGENIUM DNS  │                                 │ 185.204.169.26│                                 └──────────────┘

Python SDK

A Python version (agenium-mcp-server) is planned. For now, use the npm package.

License

MIT

Source: packages/mcp-bridge/README.md at commit 9103e1a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts