Refunds.docx
Escalation.pdf
Disputes.md
Refund steps
Escalation
Disputes
Word docs, PDFs or wiki exports in. Guides with tip and warning steps out, filed where they belong.
From a folder of docs
Built on the Model Context ProtocolNobody likes writing docs.
Now nobody has to.
Ask the AI agent you already use to create guides for you. Let it walk through your process, capture every step and upload the finished guide in Guidejar before your coffee’s ready.
Server
https://mcp.guidejar.com/mcpBring your own agent
ChatGPT
Claude
Grok
Cursor- or any MCP client
claude — ops
✻ Claude Code 2.1 · connected to guidejar, chrome
└ chrome::navigate → new.expensify.com
└ chrome::click → + icon, “Create expense”, then 4 more · 6 screenshots
└ guidejar::get_upload_url → 6 screenshots attached
└ guidejar::create_guide → 6 steps, filed under Finance
How to create a travel expense in Expensify
1. Click the + icon · 2. Click “Create expense” · 3. Choose your start location · 4. Choose your stop location · 5. Submit the expense · 6. There you go
✦ Added a tip on step 5: Expensify works out the amount from the distance.
What you can create
Give the agent the source.
Get back finished guides.
Guidejar MCP has full write access, so an AI agent can create guides and long-form articles, upload screenshots, and file everything into folders. You review the result instead of writing it.
src/features/
billing/ → 4 guides
settings/ → 7 guides
integrations/ → 5 guides
Run Claude Code or Codex in the repo. It reads what customers actually see and writes the guide to match.
For SaaS teams
A help guide for every feature, written from your code
Step 3: Open Finance, then Refunds
Step 3: Open Billing, then Refunds
Link unchanged · updated just now
A process changed? Tell the agent. The guide is fixed in place and keeps its link.
Keep it current
Update a guide without opening the editor
Then, the easy part
Once the guides exist, the team just asks
Everyone connects the same MCP server to the chatbot they already use and asks in plain language. The assistant searches your workspace and replies with the steps and a link to the full guide.
“What’s our process for escalating a support ticket?”
Full read and write
Eleven tools, not a read-only search box
- search_guides
- list_guides
- get_guide
- create_guide
- create_article
- update_guide
- update_article
- get_upload_url
- get_teams
- get_team_folders
- get_id_from_guide_url
Ask your agent to…
Copy a prompt. Get a guide back.
Works in Claude, ChatGPT, Codex and Cursor once Guidejar is connected.
“Create guides for every process in this folder. Use warning steps for anything irreversible.”
“Go through src/features/billing and write a help guide for every customer-facing feature.”
“The refund flow changed. Update "Handle a refund request" so step 3 goes through Billing.”
“Write a long-form article on our expense policy and link the three related guides.”
“Document the new onboarding flow now that this PR is merged. Same folder as before.”
“Read the settings module and create a guide for each thing a customer can configure.”
For SaaS teams
Point your AI agent at your codebase. Get a help guide for every feature.
Your product already describes itself in code. Run Claude Code or Codex inside the repo with Guidejar connected, and it turns each feature into a step-by-step guide your customers can follow, ready for your help center.
Reads the feature, not a spec
The agent works from your routes, components and copy, so the guide matches what customers actually see.
One guide per feature, filed by area
Billing, settings, integrations. It creates a folder per area and a guide per feature, with warning steps where a change is hard to undo.
Re-run it when you ship
Merged a change to onboarding? Ask the agent to update the onboarding guides. Links stay the same, so your help center never points at a stale page.
claude — ~/acme-app
> Go through src/features/billing and create a Guidejar help guide for every customer-facing feature. File them under Billing and add a warning step wherever a change affects the next invoice.
- ⏺guidejar:get_team_folders → Found folder "Billing"
- ⏺guidejar:create_guide → Set up a payment method · 8 steps
- ⏺guidejar:create_guide → Change your billing cycle · 6 steps · 1 warning
- ⏺guidejar:create_guide → Download past invoices · 4 steps
- ⏺guidejar:create_guide → Cancel a subscription · 5 steps · 2 warnings
Created 4 guides in Billing. Two of them cover changes that affect the next invoice, so I added warning steps there. Want me to link them from the billing article?
Setup
Can't get any easier than this
No API keys to copy around and nothing to install. Add the server to your AI tool, approve access with your Guidejar login, and start creating.
Setup steps for your tool
- Open Settings → Connectors → Browse connectors and search for "Guidejar".
- Click Connect to Claude.
- Authorize the connection in your browser.
Using n8n, Zapier or another client? Any tool that supports remote MCP works with the same URL.
Security
Your workspace stays yours
The server follows the current MCP authorization spec, and the only thing it can reach is your Guidejar workspace.
OAuth sign-in
You sign in with your Guidejar account. There are no API keys to paste into a chatbot and nothing to rotate.
Scoped to your workspace
The server reaches guides and articles in Guidejar and nothing else. An agent gets the permissions your account has, not more.
One connection per teammate
Each person connects with their own login and sees only what is shared with them.
Included in Plus and above
Available on Plus and Business, with no add-on to buy. Compare plans.
Read the security best practices before connecting third-party agents.
Frequently asked questions
If you can’t find what you’re looking for, email us at [email protected]
Can an AI agent really build guides for me?
Yes. Describe a process, or point Claude Cowork, Codex or Claude Code at a folder of existing documents, and it writes a structured guide for each one with the right step types, filed into folders. You review and publish. See the Claude walkthrough or the Codex version
Can it document my product from the codebase?
Yes. Run Claude Code or Codex inside your repo with Guidejar connected and ask it to create a guide for each customer-facing feature. It reads the code, writes the steps, and files the guides in your workspace. Re-run it after a release to update the affected guides.
Can it add screenshots?
Yes, the MCP server includes an upload tool, so an agent that can capture or generate images can attach them to steps. Guides created without images can be opened in the editor to add screenshots or a recording later.
What is the Model Context Protocol?
MCP (Model Context Protocol) is an open standard that lets AI assistants such as ChatGPT and Claude securely connect to outside tools and data. Guidejar MCP is our official server for it, so those assistants can read and write your Guidejar workspace. Learn more about MCP
Which AI tools work with Guidejar MCP?
ChatGPT, Claude (including Claude Cowork and Claude Code), OpenAI Codex, Cursor, Grok and Raycast are documented step by step. Any other client that supports remote MCP servers, such as n8n or Zapier, works with the same URL.
Is my data secure?
Yes. You sign in with your Guidejar account through OAuth and can revoke access at any time. The server reaches only your Guidejar workspace, and the AI client gets the same permissions your account has, nothing more.
Can my team search the guides too?
Yes. Once the guides exist, everyone on the team connects the same server to their own chatbot and asks questions in plain language. Each member signs in with their own account and sees only the guides shared with them.
Which plan do I need?
Guidejar MCP is included in the Plus plan and above. In Claude, install it from the connector directory. In ChatGPT, it needs custom connectors, which come with ChatGPT Plus or Pro. Compare plans
Write the guides
you keep putting off.
Connect Guidejar to Claude, ChatGPT or Grok, and the next feature you ship comes with its help guide already written.
