@breadai/protocol-mcp-server

Expose bread agents, tasks, tools, and agent+skill combinations as Model Context Protocol tools — over stdio (bread as an MCP child process) or Streamable HTTP mounted on bread's own server at /mcp, gated by whatever auth strategy the app configures. Both transports serve the 2025-11-25 and 2026-07-28 protocol revisions from the same endpoint/connection, with localhost-only DNS-rebinding protection on by default (allowedHosts to widen it).

bun add @breadai/protocol-mcp-server   # or: npm i @breadai/protocol-mcp-server

import { defineConfig } from '@breadai/core'
import { mcpServer } from '@breadai/protocol-mcp-server'

export default defineConfig({
  entrypoints: ['researcher'],
  plugins: [
    // List mcpServer last: its stdio transport snapshots other plugins' tools at init.
    mcpServer({
      transport: 'http', // or 'stdio' (default)
      agents: ['researcher'],
      tasks: ['extract'],
    }),
  ],
})

Exposed agents run via bread.run(..., { mode: 'sync' }) with real input/output schemas; tasks keep their full hook chain and crumbs.

Part of bread — an explicit-by-design framework for AI agents. Docs: MCP server · all docs.

License

MIT © Matteo Zambon