Barndoor Automations documentation
Build, run and connect Blueprints
A Blueprint is a callable AI service. Run it from the API, an MCP client or the SDKs, and connect it to the tools your team already uses.
⌘K
Guides people start with
All guides- Run your first Blueprint in Diaphora cloudConnect your tools, write a blueprint, deploy it, and call it — the shortest path to a real, cloud-hosted run with a stable API endpoint, MCP tool, and optional schedule.7 min
- Running Frags LocallyInstall the open-source Frags CLI, point it at Gemini, ChatGPT, Anthropic, or Ollama, and run your first Blueprint on your own machine.5 min
- Setting up toolsAdd a new connection to tools.json end-to-end — OAuth for an MCP server, a Postgres collection, and where apicp fits in — then verify it before wiring it into a blueprint.4 min
- Building automations with Barndoor MCP serversRoute a tools profile through Barndoor's governed MCP gateway — register the Diaphora connector, set the OAuth redirect, scope an access policy, and verify every server resolves to ready before a Blueprint calls it.7 min
Find what you need
All docsGuides
Task-by-task walkthroughs, from the first run to production.
15 guidesAPI reference
Every endpoint, parameter and response, with runnable examples.
4 endpointsMCP reference
Tools and connectors a Blueprint can use, and how to add your own.
Connecting systemsPython SDK
Typed client with sync, streaming and MCP tool calls.
pip install diaphora-pythonTypeScript SDK
Typed client for Node and edge runtimes, with streaming callbacks.
npm install diaphora-typescriptWorkflows
How a Blueprint defines sessions, tool calls and typed output.
The whole system