AgentRuntime MCP SDK (TypeScript)

Opinionated SDK aligned with agentruntime-mcp-go, built on the official @modelcontextprotocol/server streamable HTTP transport (JSON responses).

Note: Same config.yaml shape and Control integration as the Go SDK (POST /mcp/config, optional env overrides per schema key, GET …/config/schema). Legacy FastMCP-only flows are removed.

Releasing

See ../RELEASE.md (TypeScript section): bump package.json, npm run build before publish, do not commit node_modules/ or dist/.

Install

npm install @agentruntime-labs/agentruntime-mcp zod @cfworker/json-schema

Minimal example

import { z } from "zod";
import { tool, run } from "@agentruntime-labs/agentruntime-mcp";

const In = z.object({
  a: z.number(),
  b: z.number(),
});

const Out = z.object({
  result: z.number(),
  expression: z.string(),
});

tool({
  name: "add",
  description: "Add two numbers",
  inputSchema: In,
  outputSchema: Out,
  execute: async (args, config) => {
    // Resolved config from control server is exposed here.
    const region = config.region as string | undefined;
    return {
      result: args.a + args.b,
      expression: `${args.a} + ${args.b}`,
    };
  },
});

run("config.yaml");

Config

• config.yaml controls server host/port, optional reserved auth keys, tracing, and the Control config schema.
• Env overrides: HOST, PORT. Control integration uses MCP_CONTROL_SERVER_URL, MCP_CONFIG_FETCH_REQUIRED, etc. (see docs/mcp/mcp_env.md); there is no mandatory FastMCP-style global token middleware — the run token arrives on the HTTP request.

Example config.yaml:

server:
  name: "MCPAuthDemo"
  host: "127.0.0.1"
  port: 8012
  stateless_http: true

auth:
  mode: token   # reserved for templates; Control uses request Bearer token

tracing:
  enabled: false

config:
  accessKeyId:
    type: string
    displayName: Access Key ID
    required: true
  secretAccessKey:
    type: string
    displayName: Secret Access Key
    required: true
  bucket:
    type: string
    displayName: Bucket
    required: true
  region:
    type: option
    displayName: Region
    required: true
    options:
      - label: Default
        value: us-east-1
      - label: US East (Ohio)
        value: us-east-2

Auth modes

• none: no auth
• token: Authorization: Bearer <token> or X-MCP-Token; dev fallback ?auth_token= if ALLOW_QUERY_TOKEN=true
• hmac: headers X-MCP-KeyId, X-MCP-Timestamp (unix seconds), X-MCP-Signature (hex(HMAC-SHA256(secret, ${ts}\n${method}\n${path})))

Control config resolution

The SDK can resolve populated config values from a control server and expose them on the request context as config in tool handlers.

• Set MCP_CONTROL_SERVER_URL (e.g. http://control-svc:8080)
• SDK sends POST /mcp/config with your config.yaml config: schema
• SDK forwards auth token from middleware (Authorization / X-MCP-Token)
• SDK also forwards best-effort runtime_context for control-side policy/resolution
• Returned populated config is exposed as config in the tool execute callback

Environment flags:

• MCP_CONTROL_SERVER_URL: control server base URL
• MCP_CONTROL_TIMEOUT_SEC: request timeout (default 5)
• MCP_CONFIG_FETCH_REQUIRED: fail request if resolution fails (default true)

Schema endpoint:

• GET /mcp/config/schema returns the raw config: schema from config.yaml.

Proxy (library)

import { runProxy } from "@agentruntime-labs/agentruntime-mcp";

await runProxy(
  "http://127.0.0.1:8000/mcp",
  "tools.yaml",
  undefined, // bearer token
  "127.0.0.1",
  8010
);

Tool organization (toolorg)

import { publisherMetadata } from "@agentruntime-labs/agentruntime-mcp"