import { McpBridge } from '@svantic/sdk';

import { McpBridge } from '@svantic/sdk';

// 1. Create the bridge with a label (used in logs and errors).
const bridge = new McpBridge('filesystem');

// 2. Spawn the MCP server and handshake.
await bridge.connect({
  command: 'npx',
  args: ['@modelcontextprotocol/server-filesystem', '/data'],
});

// 3. Introspect what's available.
const tools = await bridge.list_tools();
console.log(tools.map((t) => t.name));

// 4. Call a tool directly. Arguments match the MCP server's JSON Schema.
const result = await bridge.call_tool('read_file', {
  path: '/data/notes/today.md',
});

// 5. Always close — otherwise the child process leaks until GC.
await bridge.close();

interface McpServerSpawnConfig {
  command: string;
  args?: string[];
  env?: Record<string, string>;
}

{ command: 'npx', args: ['@modelcontextprotocol/server-filesystem', '/path'] }

interface McpToolDescriptor {
  name: string;
  description?: string;
  input_schema: Record<string, unknown>;
}

new McpBridge(server_name: string)

await bridge.connect({ command: 'npx', args: ['chrome-devtools-mcp@latest'] });

const bridge = new McpBridge('filesystem');

await bridge.connect({
  command: 'npx',
  args: ['@modelcontextprotocol/server-filesystem', '/data'],
});

const tools = await bridge.list_tools();
const result = await bridge.call_tool('read_file', { path: '/data/note.md' });

await bridge.close();