@xmcp-dev/cli

CLI tool for generating typed clients from xmcp MCP servers external connections.

Usage

npx @xmcp-dev/cli generate [options]

Client Configuration

Define everything in src/clients.ts to use the full feature set:

export const clients = {
  figma: {
    url: "https://mcp.figma.com/mcp",
    headers: [{ name: "x-api-key", env: "FIGMA_TOKEN" }],
  },
  playwright: {
    npm: "@playwright/mcp@latest",
    args: ["--browser", "chromium"],
    env: { DEBUG: "pw:api,pw:browser*" },
  },
  firecrawl: {
    npm: "firecrawl-mcp",
    env: { FIRECRAWL_API_KEY: process.env.FIRECRAWL_API_KEY ?? "" },
  },
  context7: {
    command: "bunx",
    args: [
      "-y",
      "@upstash/context7-mcp",
      "--api-key",
      process.env.CONTEXT7_KEY!,
    ],
  },
};

• Entries with a url use the HTTP transport (optional headers are supported, just like before).
• Entries with npm (optionally command, args, env, cwd, stderr) use STDIO. The CLI runs command (defaults to npx) with [npm, ...args] and passes through env.
• API keys can be provided either as CLI args (e.g., ["--api-key", process.env.CONTEXT7_KEY!]) or via the env map. Prefer env for secrets.
• STDIO packages must already be installed in the environment the CLI runs in (global install, workspace dependency, or cached npx package).

Run npx @xmcp-dev/cli generate to produce the typed client files.

Optional CLI flags

• -c, --clients <path>: Custom path to clients.ts (default src/clients.ts).
• -o, --out <path>: Output directory (default src/generated).

Generated Output

For each client defined in clients.ts, the CLI generates a client.{name}.ts file containing:

• Zod schemas for each tool's arguments
• Type exports (e.g., GreetArgs)
• Tool metadata objects
• createRemoteToolClient() factory function
• Pre-instantiated client export

An index file (client.index.ts) is always generated with a unified generatedClients object:

import { generatedClients } from "./generated/client.index";

await generatedClients.client1.greet({ name: "World" });
await generatedClients.client2.randomNumber();

Caveats

• Server/process must be available — The CLI connects over HTTP or spawns the STDIO package to fetch tool definitions. Ensure the remote server is reachable or the npm package is installed and executable in your environment.
• clients.ts required — The CLI generates clients only from the definitions you provide (or the path you pass with --clients).