Document Your Team's SOPs with AI in an Afternoon (Using Codex + Guidejar)

Do not index

The processes that keep your team running are mostly undocumented. How to file an expense claim. How to update a deal in Salesforce. How to onboard a new hire. That knowledge lives in a few people’s heads — and gets re-explained over Slack every single week.

Writing it all down has always been the bottleneck. Not for lack of will, but because creating SOPs by hand — one standard operating procedure at a time, formatting each step, organizing it so people can actually find it — eats hours nobody has.

That changes when you connect OpenAI Codex to Guidejar MCP. Codex is an AI agent, not just a chat window — it works directly with the files and folders already on your machine. Point it at a folder of old process docs, or just describe how your team works, and it builds a polished step-by-step guide for each one, sorts them into folders, and reports back when it’s done.

You describe what your team does. Codex builds the playbook.

First, What Is Guidejar?

Guidejar is a tool for turning everyday “how do I…?” questions into clear, interactive step-by-step guides — for your team or your customers. Instead of long, text-heavy documents nobody reads, you get visual walkthroughs that show people exactly what to do, click by click. It’s already trusted by 10k+ users and teams at companies like DHL, Avallain and Visma.

So why keep your SOPs in Guidejar instead of a folder of Google Docs or a Notion page?

Guides people actually follow. Step-by-step walkthroughs with screenshots and callouts are far easier to follow than a wall of text — especially for new hires and non-technical teammates.

Everything in one searchable place. Group guides into a branded help center or internal wiki so people can find answers themselves instead of pinging you on Slack.

Hosted on your own domain. Publish your knowledge base at help.yourcompany.com with your logo and colors — it feels like part of your product, not a third-party tool.

Private when it needs to be. Role-based access control and optional authentication keep sensitive internal docs locked to the right people.

Built for teams. Invite your whole team into one workspace, with roles that control who can view and edit.

Embeds anywhere. Drop guides straight into Notion, Confluence, Salesforce, your website, or your help docs.

In short: Guidejar is purpose-built to be the home for your processes — clear to follow, easy to find, and branded as your own. The rest of this guide shows how to fill it, fast.

Why Codex (Not Just a Chatbot)

A regular AI chat lives in a box. You can paste text into it, but it can’t reach the files and folders sitting on your computer. You type a prompt, wait, review, type the next one — and you have to hand-feed it everything.

Codex is different. It’s an AI agent that works directly with your local files and folders — the documents, spreadsheets, PDFs, and exports already sitting on your machine. Instead of copy-pasting content one piece at a time, you point it at a folder and let it work through the whole job.

That’s the real unlock for documentation. The processes you want to write up are usually already half-documented somewhere — a folder of Google Docs, a stack of PDFs, an old SOP spreadsheet. Codex can open all of it, understand it, and turn it into polished guides. And because it’s an agent, it works through the job step by step and checks in when it’s done — no babysitting each prompt.

So you can:

Point it at a folder of existing documents and let it convert every one into a clean guide

Hand it a list of 20 processes and walk away while it builds each one

Ask it to audit what you already have in Guidejar and fill the gaps

Have it build an entire onboarding program — guides, articles, and folders — from one prompt

What Is Guidejar MCP?

MCP (Model Context Protocol) is a standard way to connect AI tools like Codex to outside services. Connecting Guidejar MCP gives Codex a direct line to your Guidejar workspace, so it can:

Create guides — turn a described process into a step-by-step guide

Create articles — write longer reference documents like policies

Search guides — check what’s already documented

Read guides — pull up existing content

If you can describe a process in plain English, Codex can build it.

Setting It Up (Under 5 Minutes)

Guidejar MCP is a remote, OAuth-based MCP server, so you do not need to run a local bridge like mcp-remote. Codex can connect to the Streamable HTTP endpoint directly.

You’ll need a Guidejar account and Codex installed.

Add Guidejar’s official MCP endpoint to Codex:

codex mcp add guidejar --url https://mcp.guidejar.com/mcp

If you prefer editing your Codex config manually, add this to ~/.codex/config.toml:

[mcp_servers.guidejar]
url = "https://mcp.guidejar.com/mcp"

Authorize Codex to access your Guidejar workspace:

codex mcp login guidejar

Codex opens a browser-based OAuth flow. Sign in to Guidejar and approve the connection.

Start a new Codex session, then run /mcp to confirm Guidejar is connected.

That’s it. Codex can now use Guidejar’s MCP tools to search, list, and read your existing guides, then create new guides and articles in your workspace.

How to Use It: Real Examples

Document an Entire Department in One Go

This is where Codex earns its keep. Instead of creating guides one at a time, hand it the whole list:

“Here are the 12 processes our customer support team handles daily. Create a guide for each one and put them all in the Customer Support folder: 1. Responding to a new ticket in Zendesk 2. Escalating a ticket to Tier 2 3. Processing a refund request 4. Updating a customer’s billing info 5. Handling an angry customer 6. Closing and tagging a resolved ticket…and so on. Use warning steps for anything involving refunds or account changes.”

Codex works through all 12 — creating each guide, placing it in the right folder, and adding the right step types along the way. You check back in a few minutes and your support team’s entire playbook exists.

Turn a Folder of Documents Into Guides

This is the one a chatbot simply can’t do. Got a folder full of Word docs, PDFs, or exported wiki pages describing how things work? Point Codex straight at it:

“Look in my Team SOPs folder. For every document in there, create a matching Guidejar guide with clear steps. Use heading steps for section breaks, and add a warning step for anything that mentions a contract or legal sign-off. Put them all in the Operations folder in Guidejar.”

Codex opens each file itself, figures out the logical steps, picks the right step types, and builds a structured guide — for every document in the folder. No copy-pasting, no doing them one at a time. What would take you days of reformatting happens while you grab a coffee.

Audit What You Have and Fill the Gaps

Already have some guides in Guidejar? Let Codex review them and tell you what’s missing:

“Search all my Guidejar guides and list what processes we’ve already documented. Then tell me which common HR and IT processes are missing — things like password resets, equipment requests, or leave policies.”

Codex searches your workspace, reviews what’s there, and hands you a gap analysis. Then follow up:

“Create guides for the top 5 missing processes you found. Put them in the right folders.”

Build a Complete Onboarding Program

“Build a full onboarding program in Guidejar for new marketing hires: - A ‘Welcome’ guide with chapters for company overview, team structure, and the tools we use - Separate how-to guides for HubSpot, Google Analytics, and our content calendar in Notion - An article covering brand guidelines and tone of voice Put everything in the Onboarding folder.”

One prompt. Multiple guides, an article, and a folder structure — all built and organized. Codex handles the complexity: interactive walkthroughs with chapters, step-by-step how-tos, and a long-form policy article, each in the right place.

Every Guide Is a Polished, Shareable Page

Here’s the part that makes this more than a documentation dump: every guide Codex creates becomes a clean, professional-looking page — not a wall of text in a doc.

Each one gets its own shareable link you can drop into Slack, an email, or a help center. Steps are laid out clearly, screenshots and callouts render properly, and the whole thing looks like something your company would actually be proud to send a customer or a new hire.

And it’s yours to brand. You can host your guides on your own custom domain — so instead of a generic link, your team and customers see guides.yourcompany.com. Same guides Codex built, served from your domain, matching your brand. It feels like a polished internal knowledge base you spent weeks building, except Codex built it in an afternoon.

Your Whole Team Can Get Answers — From Any Chatbot

Creating the guides is only half the value. Once they’re in your Guidejar workspace, everyone on your team can ask questions against them using the exact same Guidejar MCP — no Codex required.

Each teammate connects Guidejar MCP to whatever AI tool they already use — ChatGPT, Claude, or any other MCP-compatible chatbot — and starts asking questions in plain language:

“How do I file an expense claim?”

“What’s our process for escalating a support ticket?”

“Where do I update a customer’s billing info in Salesforce?”

The chatbot searches your team’s Guidejar workspace and answers instantly, pulling straight from the guides you built — with a link to the full guide if they want the step-by-step. No more interrupting a colleague, digging through a shared drive, or asking the same question in Slack for the third time.

So the workflow splits cleanly:

You (or whoever owns processes) use Codex to build the knowledge base at scale.

Everyone else uses ChatGPT or Claude to get answers from it, instantly, all day long.

One workspace. The whole team self-serves.

Tips for Getting Better Guides

Tell Codex which step types to use. Guidejar supports different step styles, and you can ask for them by name:

Tip — for helpful reminders (“Save your progress before switching tabs”)

Warning — for things that can go wrong (“This action can’t be undone”)

Heading — for section breaks in longer guides

Chapter — for interactive walkthroughs with clickable buttons, great for onboarding

Ask for FAQs on common process guides. Just describe them:

“Add FAQs: ‘How long does approval take?’ — ‘Usually 2-3 business days.’ and ‘What if my manager is out?’ — ‘It routes to their backup approver automatically.’”

Have Codex organize as it goes. Tell it which folder each guide belongs in, and it’ll place them correctly — or even create a sensible structure for a batch.

One guide per process. Keep each guide focused on a single task. “How to Submit a PTO Request” beats “Everything About Time Off” — people search for specific answers.

Review the results. Codex does the heavy lifting, but you know your processes best. Skim the finished guides, then ask Codex to tweak anything that’s off: “In the refund guide, add a step about checking the original payment method first.”

Why This Beats What You’re Doing Now

Most teams keep processes in shared Google Docs, buried Notion pages, or Slack threads that vanish in the scroll. The documentation either doesn’t exist or nobody can find it.

Codex plus Guidejar MCP fixes both problems at once. You describe your processes the way you’d explain them to a new colleague, and Codex builds them into clean, searchable, step-by-step guides — at scale. A chat lets you create one guide in 30 seconds. Codex lets you build your team’s entire knowledge base in an afternoon.

Your team gets answers without asking. You stop being the help desk.

FAQ

Do I need to be a developer to use this? Codex is a developer-oriented tool, so the one-time setup involves adding Guidejar as an MCP server in your Codex config. After that, building guides is as simple as describing a process in plain English — no coding required.

What is an SOP library? An SOP (standard operating procedure) library is a single, organized home for every repeatable process your team runs — onboarding, refunds, approvals, and more — so people can find the right answer themselves instead of asking around.

What’s MCP? MCP (Model Context Protocol) is an open standard for connecting AI tools to outside services. Guidejar MCP gives Codex a direct line to create, search, and read guides in your Guidejar workspace.

Can my whole team use the guides? Yes. Once guides live in your Guidejar workspace, anyone can connect Guidejar MCP to ChatGPT, Claude, or any MCP-compatible chatbot and ask questions against them — no Codex required.

Get Started

Connect Guidejar MCP in Codex using the server URL: https://mcp.guidejar.com/mcp

Hand Codex your first list of processes and watch the guides appear

For setup help, visit the Guidejar MCP documentation.