Skip to content
Docsie Logo

Docsie MCP server · Apps, agents and factories

Extend Docsie with your own apps, skills and agents.

Build an app with Claude Code and install it into Docsie. Add skills that shape rewrites and workflow steps, run one Docsie app over many documents or videos with a factory, and hand longer jobs to Docsie's own background agent.

Connect your AI tool →Book a demo

Installing apps and skills through Workflow Builder needs the Business plan or higher. Factories and the apps they run use AI credits.

https://app.docsie.io/mcpWorks in Claude, ChatGPT, Claude Code, Cursor, Codex and any MCP client.
A skill package in Docsie Skills and Agents, showing the SKILL.md source for a maintenance house style and a parts.md file
01

A skill, as Docsie stores it

The maintenance-style skill package in Skills & Agents, with its SKILL.md rules for numbered steps and a Before you start list, and a parts.md reference file.

What you can ask

Ask for the bigger jobs.

Three ways to extend Docsie from your assistant. Write and install an app, run an app over many files with a factory, or hand a job to a Docsie background agent.

Claude Code

“Build a Docsie app for tracking equipment calibration, with a screen per asset and a data table for due dates, and install it in my workspace.”

  • packages.create
  • apps.install

Claude Code writes app.json, SKILL.md and the screen files locally, installs the package through Workflow Builder, and its screens show up as Docsie tools.

Cursor

“Set up a document review factory that checks every supplier SOP against our approved baseline. Show me a sample first.”

  • factory_create · document_review
  • factory_add_documents
  • factory_control · sample

A sample result to approve. Once you approve it, the rest run and only the exceptions come back for review.

ChatGPT

“Have Docsie's agent turn this Loom recording into a guide and put it in the Field Service book.”

  • docsie_agent_start
  • docsie_agent_status
  • docsie_agent_result

Docsie's own agent works through the steps in the background, using only the packs this connection has, and reports what it did.

Watch it work

See factories, skills and workflows in Docsie.

Walkthroughs recorded in the Docsie app. Over MCP, your assistant runs the same app and gets the same results back in the chat.

Review documents at scale with Docsie FactoriesA Document Review Factory checks a whole batch of documents against the same approved baseline. Configure the review once, run it across many documents, and spend your time on the exceptions.
Build your first Docsie skill: SKILL.md and a reference fileA house style for maintenance procedures as a Docsie skill: the rules in SKILL.md and the part names in a reference file, uploaded in Skills & Agents and applied to a rewrite.Recorded in Docsie's test environment with a fictional company (Acme Manufacturing). No customer documents.
Give a workflow step a shelf: fixed, from input, or after every rewriteHow a Docsie workflow step chooses which shelf it works on: a fixed shelf, a shelf passed in as input, or the shelf of every finished rewrite.Recorded in Docsie's test environment. No customer documents.

How it works

How to build and install a Docsie app.

Write it with Claude Code

An app is a package. It holds app.json with its screens and data tables, a SKILL.md and the screen files, and Claude Code writes them on your machine.

Install it into Docsie

Install it through the Workflow Builder MCP gateway, or upload the zip in Skills & Agents, then Apps. Its screens become Docsie tools.

Run it, or run it at scale

Use the new tools from your assistant, or run a Docsie app over many documents or videos with a factory. Approve a sample, and it runs the rest and sends only exceptions to review.

Permissions and limits

What to tick, and what it costs.

Packs and plan

Installing through the Workflow Builder MCP gateway needs Business or higher. Creating, adding to and running factories needs Workspace create and edit; reading them needs search and read.

AI credits

Factories have no plan gate. They use your organization's AI credits for every document or video they process.

FAQ

Common questions

Can Claude Code build a Docsie app?

Yes. Claude Code writes the app package on your machine, with app.json for screens and data tables, a SKILL.md and screen files. You install it into Docsie through the Workflow Builder MCP gateway or by uploading the zip in Skills & Agents. Docsie's built-in Analytics and API docs apps are built the same way.

What is a Docsie skill?

A SKILL.md package with your rules, added through Workflow Builder on Business and up. Docsie applies it to rewrites and workflow steps.

What is a Docsie factory?

A way to run one Docsie app over many documents or videos. You approve a sample first, then it runs the rest and sends only the exceptions to review. The live templates are Document review, Video to Docs and Showcase.

What does a Docsie background agent do?

docsie_agent_start hands a multi-step request to Docsie's own agent, which works in the background. Your assistant follows it with docsie_agent_status, reads docsie_agent_result, or stops it with docsie_agent_cancel. The agent can only use the packs your connection has.

Which plan do I need?

The MCP server is on every Docsie plan. Installing apps and skills through Workflow Builder needs Business or higher. Factories have no plan gate and use AI credits.

Docsie MCP server

Fit Docsie to your team's work, from the tools you already use.

Connect Claude Code, Cursor or ChatGPT to Docsie, install your own apps and skills, and run factories and agents from the chat.

Connect your AI tool →Book a demo