mcpai

An MCP server that embodies the Budd-ie agent (and any other agent definitions you drop into agents/). It exposes "everything" the protocol supports — tools, prompts, and resources — so any MCP client (Claude Desktop, the MCP Inspector, Cursor, etc.) can converse with the agent in character or introspect its definition.

Agent definitions

Agents live in agents/ as JSON in the Open WebUI model-export format. agents/budd-ie.json is included (source: Budd-ie on Open WebUI by @casp-el-oper). Any *.json file placed here is loaded automatically at startup; a single file may contain one object or an array of objects.

What it exposes

Resources

| URI | Description | | --- | --- | | agent://index | JSON list of all agents | | agent://<id> | Full definition of one agent | | agent://<id>/system | Raw system prompt (markdown) |

Prompts

| Name | Args | Description | | --- | --- | --- | | <id> (e.g. budd-ie) | message | Chat with the agent, seeded with its system protocol |

Tools

| Name | Args | Description | | --- | --- | --- | | list_agents | – | List all agents with tags/descriptions | | get_agent | id | Full definition for one agent | | ask_agent | id, message | Wrap a question in the agent's system protocol | | echo | text | Connectivity check |

Quick start

npm install
npm run build
npm start           # runs the server over stdio

Try it with the MCP Inspector

npm run build
npm run inspect

Use with an MCP client

Add to your client's MCP config (e.g. Claude Desktop claude_desktop_config.json):

{
  "mcpServers": {
    "mcpai": {
      "command": "npx",
      "args": ["-y", "@caspav85/mcpai"]
    }
  }
}

Or point directly at a local build:

{
  "mcpServers": {
    "mcpai": {
      "command": "node",
      "args": ["/absolute/path/to/mcpai/dist/index.js"]
    }
  }
}

Development

npm run dev         # tsc --watch
npm run typecheck   # type-check without emitting

License

Apache-2.0