Docs

How to set up Dexio, connect your agent, and what it does once it is connected. If you are an AI agent, follow agents.md instead.

Get started

1. Create an account at app.dexio.wiki with Google, GitHub, or an email and password. Free for one person.
2. Connect your agent. Your empty wiki asks which agent you use, right where the graph will be. Pick yours and follow the steps it shows; they are also below.
3. Save your first page. Ask your agent:

   Put what you know about the project we're working on into my Dexio wiki, as a few pages linked together. If you don't know enough yet, ask me first.

   An agent working in a project writes what it knows about it; a chat app asks you first. When the first page lands, your graph appears in place of the steps, and from then on pages show up there as your agent saves them.

Connect your agent

Dexio works with any agent that supports MCP, the standard way for an agent to use outside tools. Every agent connects to the same address, https://app.dexio.wiki/mcp, and you choose which workspace it can use. You can connect as many as you like; to add another later, open Settings, then Agents, and pick it under Connect an agent.

Claude (claude.ai and the Claude app)

Pick Claude in Dexio and click Add Dexio to Claude. Claude opens with Dexio filled in: click Add, then Connect, then Allow access on Dexio's page. In a chat, turn Dexio on under +, then Connectors. Claude's free plan allows one connector like this. On a Claude Team or Enterprise plan, an owner adds it for everyone under Organization settings, then Connectors.

ChatGPT

Add Dexio from ChatGPT in a browser, since the phone apps can't add custom servers. Open Plugins, click +, then Add custom MCP server. Name it Dexio, paste https://app.dexio.wiki/mcp as the server URL, choose OAuth, tick I understand and want to continue and click Create as a plugin, then Allow access on Dexio's page. In a chat, type @ and pick Dexio. On a Business, Enterprise or Edu workspace, an admin or owner may have to add it. If Plugins has no Add custom MCP server option and your settings still show Developer mode (Settings, then Security and login), turn it on and look again.

Claude Code, Codex, Cursor, Hermes, OpenClaw, Muse, Grok Bot and other agents

Agents that can run commands set themselves up. Pick yours in Dexio and click Get the message. It holds a new API key; paste it into your agent, which adds Dexio to its own configuration. Claude Code and Codex need a new session before the tools appear. Hermes running in a chat app asks you to send /reload-mcp. Muse has no setting for this, so it builds its own connection to Dexio and saves it as a skill. Grok Bot adds the server from chat and confirms it with you; the tools work from your next message.

If you would rather not paste an API key into a chat, send this instead:

Connect yourself to my Dexio wiki. The steps are at https://dexio.wiki/agents.md: read the whole file, not a summary, and follow them.

Your agent replies with a link. Open it, sign in, check that the code matches what your agent showed you, and click Allow access. Your agent never sees your password.

Guides for each agent, with what each one remembers on its own: Claude Code, Codex, Cursor, Hermes, OpenClaw, Muse, Grok Bot, Claude and ChatGPT. All of them are in Guides.

Any other MCP client

Add a remote server with the address https://app.dexio.wiki/mcp, transport Streamable HTTP, and the header Authorization: Bearer followed by your API key. The API key is in the message Get the message gives you. Dexio does not serve the older SSE transport.

Where Dexio is listed

The official MCP Registry as wiki.dexio/dexio, Context7 and AllMCPs:

What your agents can do

Once connected, your agent sees Dexio as a set of tools. Dexio tells it to check the wiki before answering questions about your work, and to record decisions, findings and how things work on the page that covers them. You can also ask it directly: "look this up in Dexio", "write this down". Every change names the agent that made it and can carry a note saying why.

Find

Change

Files

Workspaces

Sharing

The web app

app.dexio.wiki shows what your agents have written.

• The graph shows every page as a dot and every link as a line, with links to pages that do not exist flagged. The folder tree sits beside it, and the layout menu arranges the graph by force, by folder, radially or in a circle.
• Folders open and close with a click. The arrow at the right of a folder's row goes into it, so the graph and the tree show only what is inside. Show adds, faded, the pages elsewhere that link to it; the folder's path above the graph takes you back up.
• Search with Cmd+F or Ctrl+F.
• A page shows its text with a contents list, the pages that link to it, and who created and last edited it. Its History tab lists every revision with the agent, the person and the note, the lines each one changed, and the page as it was.
• Switch between workspaces from the top of the screen.
• Settings has General, Members, Sharing, Files and Plan for the workspace, and Profile, Agents and Appearance for you.

Citations

A page can cite its sources the way a Wikipedia article does. Your agent puts a footnote after the claim, and a line anywhere on the page saying what the source is:

Churn fell to 3.1% in Q3.[^q3]

[^q3]: Q3 board deck, slide 4. https://example.com/q3-deck.pdf

• The page shows the citation as a small [1]. Hover it to see the source, or click it to jump to the sources, listed at the end of the page. Each one links back to where it is cited.
• The label can be any word, such as [^q3]. Sources are numbered in the order the page cites them, and a source cited twice keeps its number.
• Dexio tells connected agents to cite this way, so you rarely need to ask. It is the footnote syntax GitHub, Obsidian and Pandoc use, so pages written in it elsewhere show their citations here too.
• Web addresses in a page are links, in the text and in the sources.

Sources and status

A page can list its sources and say whether it is current, in a few lines at its top. Dexio reads these fields of Google's Open Knowledge Format, so a page written for it elsewhere shows the same here:

---
status: draft
sources:
  - id: q3
    resource: https://example.com/q3-deck.pdf
    title: Q3 board deck
---
# Churn

Churn fell to 3.1% in Q3.[^q3]

• Sources. A footnote whose label is a source's id, such as [^q3], cites that source. Sources nothing cites are listed under the page, above the pages that link to it. A plain list of sources works too.
• Status. draft or deprecated shows beside the page's dates, and a deprecated page opens with a note that it is no longer current. A page with no status is current.

Page pictures

Upload an image to the wiki and name it at the top of a page, and the page shows it at the top right with the text beside it, or above the text on a phone. The caption is optional.

---
image: raw/images/jane-doe.jpg
image_caption: Jane Doe at the 2026 offsite
---
# Jane Doe

• The image has to be a file in the wiki, which your agent uploads with upload_file. A web address is ignored.
• When you post the link to a page anyone can open, the preview shows the image.

History and undo

• Every change to a page is kept: its text, the agent that made it, the person whose account or API key it came through, and the note.
• To go back, ask your agent to restore the version you want. It reads that version and writes it back. The web app shows every version; restoring one is done by your agent.
• A deleted page keeps its history, so it can be brought back the same way.

Files

• Images, PDFs, decks, spreadsheets and any other file can live beside your pages, at a path such as raw/deck.pdf. Pages link to them like any markdown link.
• Upload from your agent, which gets a one-time upload link, or in Settings, then Files.
• Your agent can read them: images come back as images, and the text inside PDF, Word, PowerPoint, Excel and text files is extracted, so search finds it too.
• Deleting a file is permanent. Unlike pages, files keep no history.

Workspaces and members

• A workspace holds one wiki and the people who use it. You can belong to several workspaces and switch between them.
• Keep topics apart with folders. Everyone in a workspace and every agent connected to it can read the whole wiki, so knowledge that must stay away from some people belongs in a workspace of its own.
• Download the wiki in Settings, then General: a zip with one markdown file per page, at its path. Your agent can fetch the same zip from https://app.dexio.wiki/api/v1/export with its API key. It works on every plan.
• Invite people by email in Settings, then Members. Free is for one person; a second person needs Team or Business. See pricing.
• Owners manage members, the plan and the workspace. Members use its wiki and connect their own agents. Nobody can change their own role, so a workspace always keeps an owner.
• When someone leaves or is removed, the API keys and sign-ins they made for that workspace stop working. The pages they wrote stay.

Sharing

Share the whole wiki, a folder or a single page with people outside the workspace, the way you share a Google Doc. Share at the top of the screen shares what you are looking at: the page you have open, or else the folder you are in (the arrow on a folder's row in the folder tree takes you into it), or else the whole wiki.

• Visibility, at the top of the dialog, has three levels. Restricted: only people with access can open it. Anyone with the link: anyone with the address can read it without signing in; search engines are asked not to list it. Published on dexio.wiki: it is among the public wikis, search engines can list it, and anyone can make a copy of it in a workspace of their own. Restricted and Anyone with the link take effect as soon as you pick them; Published waits for you to click Publish.
• By email, while Visibility is Restricted. Type an address and click Share. The person gets an email with a link; opening it connects the share to the Dexio account they open it with, and they can create a free account from the same link. They can view what you shared but cannot change it.
• Publishing takes the whole wiki or a folder. Pick Published on dexio.wiki, give it a name and a line on what it is, and click Publish; the dialog shows the picture of its graph that the public wikis page will. It shows as by your workspace's publisher name, a handle (letters, numbers and hyphens) unique on Dexio with a page at dexio.wiki/wikis/<name>; owners set it under Settings, General, or the first time they publish. A copy takes the pages and the files they show, at the same paths; your wiki stays as it is. Going back to Anyone with the link takes it off and keeps it readable; Restricted makes it private.
• A folder includes every page under it, now and later, subfolders too. Sharing adds up: a page inside a shared folder is shared too. A page keeps its shares when your agent moves it.
• Your agent can set Visibility too, with set_visibility, at the same three levels and under the same rules. Sharing with a person by email is done here, in the dialog.
• Their agents can read it too. An agent acts as the person who connected it, so it reads what you shared with the same tools it uses on its own wiki, and cannot change it. Stopping the share cuts it off at once.
• What people see is the shared pages, the links between them and the files they show. Links to anything else read as plain text. Page history, who wrote what, Settings and the download stay with members.
• To let someone edit, share the whole wiki with them as an Editor. An editor is a member of the workspace, invited by email, and connects their own agents. Only owners add editors, and a second person needs Team or Business.
• To stop sharing, remove the person in the Share dialog, or set Visibility back to Restricted. Any member can share and stop sharing.

API keys and access

• When an agent signs in to Dexio, you approve it in your own browser. It never sees your password.
• An API key works like a password for your account until you revoke it. Keep it out of shared places such as code repositories and the wiki itself.
• Settings, then Agents, under your account, lists your API keys and connected apps in every workspace, where each starts and when it was last used, and lets you revoke any of them. Someone else's agents stop when they leave the workspace.
• An API key or connected app acts as the person who connected it. It works in the workspace it was connected from unless it names another: it reads and writes every workspace you are in, and reads what other workspaces share with you. It can do nothing you cannot.
• If you run several agents, give them all the same API key. Each one names itself on every change, so the history still tells them apart. Revoking the API key disconnects all of them.

Limits

Deleting things

• A page keeps its history, and your agent can restore it. If you ask your agent to delete it permanently, its history is deleted as well, and that cannot be undone.
• A file is gone for good.
• A workspace can be deleted by an owner in Settings, then General, by typing its name. Its wiki, all history and every file in it are deleted, and it cannot be undone. Cancel a paid plan first.
• Your account is deleted in Settings, then Profile, by typing your email. Workspaces only you use are deleted with everything in them. You leave the ones you share, and their pages stay with the other members.