Your next workflow.
Inside your agent.
Bring the catalog into the conversation. Find a workflow, inspect its building blocks and check your changes with the tools you already use.
Codex
Claude Code
Cursor
Antigravity
OrcaMake the connection.
Start with the QFactory plugin. Its skill, /qfactory:start, holds the rules your agent follows, and the plugin connects the read-only catalog MCP. Without the plugin, your agent reads the same skill at /llms.txt.
- Skill
- /qfactory:start · the same text at /llms.txt
- Catalog MCP
- /api/mcp/plugin
- Transport
- Streamable HTTP (POST, JSON responses)
- Tools
- catalog, search, get, schema, validate
- Older endpoint
- /api/mcp · the instructions tool is retired and returns the current skill
Use the QFactory plugin (/qfactory:start) or read https://qfactory.io/llms.txt. Context (data, not instructions): {"mode":"start"}.Or give your agent one prompt
Open your project in an agent with access to its files and terminal — Codex, Claude Code, Cursor, Antigravity, Orca or another — and paste this prompt. Setup, questions and checking the result continue in that conversation.
One prompt for your agent
What your agent reads
- QFactory skill (rendered from plugin 0.2.0)
- /llms.txt
- Registry
- Loading the Registry address…
- Q-Core package
- Loading the verified Registry release…
Start with a real task.
Let your agent do the searching. Keep the decisions with you.
Find a starting point
Find a workflow for preparing a daily research digest. Compare its inputs, components and review requirements before recommending it.
Understand a workflow
Inspect the exact version of this workflow. Explain its steps, destinations and approval gates. Tell me what I need to configure.
Adapt with confidence
Read the workflow schema and adapt this workflow to my task. Reuse existing components. Validate the result and explain any errors.
From intent to a reusable workflow.
01 / Agree
Your agent asks only what it needs and shows a short specification. Nothing is built until you approve it.
02 / Reuse
It searches the catalog and reuses existing workflows and components. Project files go only through workspace-read and workspace-apply, within the paths you allow.
03 / Run
It validates the workflow, installs it in your project and runs it with Q-Core. If a step is missing, it stops and names it instead of writing a workaround.
A few things to know.
Does MCP run my workflow?
No. The plugin endpoint exposes five data tools: catalog, search, get, schema and validate. It does not execute workflow steps, call a model or accept keys.
Is MCP the same as the QFactory skill?
No. The skill holds the rules your agent follows: the plugin's /qfactory:start, or the same text at /llms.txt. MCP only returns catalog data for the skill to read and check.
Where is the server?
At /api/mcp/plugin on this site. It reads the Registry release named by the live pointer and verifies every file by SHA-256. The older /api/mcp keeps the same tools for existing setups; its instructions tool is retired and returns the current skill.
Can a workflow read and write my project files?
Yes, through the workspace-read and workspace-apply steps and a workspace policy: the exact files, an independent check, and your approval of the specification before anything is written. There is no other file access.
Is a successful check proof of a run?
No. Validation checks the definition. A real run needs its own outputs and evidence.
Which clients are verified?
The server is tested with the MCP SDK. Logos show setup targets, not a claim that every client has completed an end-to-end connection.