Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.dzap.io/llms.txt

Use this file to discover all available pages before exploring further.

​
What’s planned

A plugin system that lets you:
  • Register custom tools — your own functions callable by ZapBot.
  • Bind third-party data sources — bring your own API and have the agent use it.
  • Package + share plugins — publish to a registry; install with one command.

​
In the meantime

Two paths get most of the way there:

​
1. Direct tool registration via SDK-AI

If you embed the agent in your app, you can extend the runtime with your own tool definitions. The pattern follows the Vercel AI SDK tool API. See ToolFactory.ts in DZapAI for the contract.

​
2. MCP-side extension

If you connect via MCP, add additional MCP servers to your client config. Tools from any connected server are visible to the agent. 
{
  "mcpServers": {
    "dzap": { "command": "npx", "args": ["-y", "dzapai", "mcp"] },
    "my-custom": { "command": "node", "args": ["./my-mcp-server.js"] }
  }
}
This isn’t quite a plugin system — closer to “side-load whatever you want into the same client” — but it covers most extension cases until plugins ship.

​
Track progress

Watch the changelog or @dzap_io on X.