plug
Business requirements → system design → your coding agent

You define the requirements.
Plug connects the dots.

Connect endpoints from different vendors in a workflow graph. Define what each connection must deliver. Plug derives the design and brings it into your agent’s IDE through MCP.

See the workflow Business intent, carried into implementation.

A connection, thought through.

01 / 03
THE BUSINESS REQUIREMENT

“Show customers useful flight options without making them wait.”

ENDPOINT NODE GET /offers Travel app · search endpoint
EDGE / BUSINESS REQUIREMENTS A fast first response
Within 500 msUp to 60 s old
Caching explicitly permitted
VENDOR ENDPOINT NODE GET /flights Vendor A · 15-second response
Plug considers scheduled caching.

The edge defines response time and freshness. With cache permission, Plug evaluates serving eligible results from a refreshed cache and exposes the remaining assumptions.

DERIVED DESIGN
Illustrative requirements and designs; not a live analysis.ADVANCES EVERY 8 SECONDS
Nodes are endpointsEdges carry requirementsYour agent reads the design
01 / START WITH THE BUSINESS

Care about the outcome.
Make the requirements explicit.

How fast should it feel?

Define response time, acceptable freshness, and how long a customer can wait for a final result.

What must never go wrong?

Make duplicate side effects, lost work, ordering, and availability requirements part of the connection.

What matters most?

Set the priorities for each edge: correctness, latency, availability, simplicity, and cost.

You define what the business needs. Plug derives the integration design from those requirements and the system facts.

02 / THE WORKFLOW

Draw the workflow.
Define the experience.

A system is more than its APIs. Plug makes the requirements between them part of the design.

  1. 01 / CONNECT

    Add vendor endpoints

    Bring operations from your systems and different vendors into one workflow graph.

    Endpoints become nodes
  2. 02 / DEFINE

    Set QoS on each edge

    Specify response time, freshness, reliability, and the tradeoffs your business accepts.

    Connections carry intent
  3. 03 / DERIVE

    Review the design

    Plug checks the facts, composes integration patterns, and explains each recommendation.

    Decisions have reasons
  4. 04 / BUILD

    Connect your IDE

    Expose the spec through MCP so your coding agent can read and update the system design.

    Intent stays with the code

Plug derives designs deterministically. Unknown facts stay unknown, and analysis never invokes your endpoints.

Explore graphs and edge requirements
03 / FROM DESIGN TO CODE

Your system design.
In your agent’s context.

Plug exposes your workflow and its requirements through an MCP server. Add it to your agentic IDE so the agent can consult the design before changing an integration.

The workspace spec and agent instructions carry your intent into implementation. When an integration changes, the agent can update the spec and ask Plug to re-analyze it.

Set up MCP and agent guidance
THE SPEC OF RECORD.plug/
├─ workflow.yaml shared intent
├─ design-input.json declared facts
├─ design.json design + proofs
├─ design.md human-readable
└─ AGENTS.md design instructions
Coding agentPlug MCPSpec

Read → update → validate → re-analyze

Cursor / VS Code / Claude / Generic MCP
04 / TRY IT LOCALLY

Start with
one connection.

Open the workbench. Describe your systems, draw a connection, and make its requirements explicit.

Read the setup guide
FROM SOURCE / NODE 24 
git clone git@github.com:plugproject/plug.git
cd plug
nvm use
npm ci
npm run dev
Local workbench at localhost:3000

Requires repository access and Node 24. Public npm distribution is not yet available.

05 / THE PROJECT

Keep business intent
connected to the code.

Plug is early. The spec is a draft.
These are the problems we’re working on.

01

Grow the pattern knowledge.

Make remedies, obligations, and tradeoffs explicit.

 02

Bring more systems into view.

Improve workspace indexing and MCP / A2A intake.

 03

Challenge the specification.

Test the assumptions. Help define the contract.
CURRENT SCOPE

Architecture output is a design, not a deployed integration. Execution is limited to seed designs. Distribution licensing is still being decided; issues and ideas are the best way to contribute today.

YOUR REQUIREMENTS. YOUR WORKFLOW. YOUR AGENT.

From business intent
to a shared system design.

Start with the guide