Claude + Barndoor Automations

Use Barndoor Automations as the structured workflow engine in Claude to run deterministic AI workflows.

MCP Server URL

https://mcp.diaphora.ai/mcp

Copy

Guide

Run in Barndoor Automations

Export structured output

Refine in Claude

Share final narrative

Overview

How the Claude workflow fits

The Claude integration pattern is about handoff. Barndoor Automations gathers, structures, and renders the result; Claude becomes the conversational layer teams use to adapt that output into an email, memo, strategy note, or stakeholder brief.

Knowledge workers run complex enterprise AI workflows directly through the Barndoor Automations MCP server, which handles the deterministic heavy lifting — gathering data, enforcing structure, and producing reliable first-pass outputs. Claude then focuses on the high-value creative work: refining tone, brainstorming ideas, and adapting the content for the specific audience.

Instead of asking Claude to handle the entire workflow from scratch, Enterprises build Blueprints for their Knowledge works to run deterministic, reliable AI powered workflows work through its MCP server. Claude is reserved only for the high-value creative final step: editorial refinement, brainstorming, and audience adaptation. The result: dramatically fewer prompts and significantly lower token spend.

Setup

How to integrate Claude with Barndoor Automations

Barndoor Automations is exposed as an MCP server. The setup is intentionally lightweight: connect your Barndoor Automations account once, then add it as a custom connector inside Claude.

1. Start with a Barndoor Automations account

Make sure you have an active Barndoor Automations account before configuring Claude. That account is the identity layer Claude will connect through.

2. Open Claude and add a custom connector

Inside Claude, add Barndoor Automations as a custom MCP connector using the server URL https://mcp.diaphora.ai/mcp. This points Claude at its MCP surface instead of treating the workflow as a pasted prompt.

3. Complete the Barndoor Automations IAM login flow

When Claude initiates the connection, you will be redirected into the Barndoor Automations IAM login process. Authenticate there to authorize the connector.

4. Return to Claude and start using Barndoor Automations tools

Once the IAM flow is complete, Claude can access Barndoor Automations as an MCP server and use connected blueprints and workflows as part of your working session.

How it works

Working with the integration

1. Run the deterministic workflow in Barndoor Automations

Start in Barndoor Automations when the job needs connector access, repeatable extraction, or schema-shaped output.

It gathers the operational context from the right tools.
The Blueprint enforces structure before any final narrative layer is added.

2. Use the rendered document as your base draft

If the Blueprint returns a document, that document is the ideal starting point for Claude. It already captures the core facts, structure, and recommended framing.

This reduces prompt thrash and cuts down on missing context.
The team starts from a finished artifact instead of a blank box.

3. Ask Claude to adapt, not reconstruct

Claude is best used to translate the Barndoor Automations output for a specific audience or purpose: a board memo, customer email, strategy note, or internal summary.

Ask for style shifts, condensation, expansion, or alternate framings.
Keep the factual backbone anchored to the original Barndoor Automations output.

4. Keep Barndoor Automations as the source of truth

When the underlying facts change, rerun the Blueprint in Barndoor Automations rather than manually rebuilding the context in Claude.

This preserves repeatability across every refresh.
Claude stays focused on collaboration instead of data wrangling.