How to Connect Outline to Claude (and What It Can't Do)
If you last checked this integration in 2025, the answer has changed. Since early 2026, every Outline workspace ships with an MCP server built in — an official one, documented in Outline’s guide. The cottage industry of community servers (Vortiago/mcp-outline and half a dozen others) still exists, but the maintainer of one popular project has already archived it, pointing users to the first-party server. For most teams there’s now exactly one sensible route.
Turning on the built-in MCP server
An admin flips it on once: Settings → AI in your Outline workspace, toggle MCP. From then on the server lives at your own wiki’s address:
https://<yoursubdomain>.getoutline.com/mcpSelf-hosters get the same thing at their own domain with /mcp appended — a nice property if you run Outline precisely because you keep your wiki on your own infrastructure. In Claude, add that URL as a custom connector (Settings → Connectors); OAuth is the default, so a browser sign-in to your Outline account appears and permissions mirror what your account can read. API-key auth via bearer header is supported too. As with all custom connectors, this requires a paid Claude plan.
Working the wiki from a chat
The official server covers search, reading, creating, and editing documents across your collections. Concretely, the kinds of requests an ops-minded Outline user makes:
- “Search the Engineering collection for the deploy runbook and walk me through the rollback section.”
- “Create a document in the Onboarding collection summarizing this Slack thread, nested under ‘First week’.”
- “Which documents in the Policies collection were edited this week, and by whom?”
Because the server can write, Claude becomes a decent wiki gardener on demand: merge two overlapping docs, restructure a collection’s landing page, turn a messy brainstorm into a properly nested document tree. Two operational notes worth knowing: OAuth tokens expire after 60 minutes (you’ll re-auth in longer sessions), and the server edits with your identity — the document history shows you.
What “on demand” rules out
A wiki’s value depends on freshness and reach — the right doc getting to the right person at the right moment — and that moment is rarely when someone happens to be chatting with Claude. Connectors can’t be invoked by anything except you, typing, in a conversation. So the incident commander at 2am doesn’t get the runbook pushed into #incidents; someone has to go ask for it. The policy update your legal team just published notifies no one. The stale-doc report you meant to run monthly runs exactly as often as you remember it.
This isn’t an Outline limitation — its API supports webhooks — it’s the boundary of what a Claude connector is allowed to be.
Making the wiki reach out: Carly
Carly is an AI executive assistant built around triggers, which is the missing half here. An incident opening, a document being updated, a first-of-the-month schedule — each can start a workflow that runs in the cloud on its own.
The setup is a conversation, not a canvas: say “when an incident is created, find the matching runbook in Outline and post it in #incidents” and Carly asks what “matching” means for your team, then builds it with you. Workflows can search collections, fetch documents, email people for real (Gmail and Outlook, attachments included), post to Slack, and file follow-up tasks. AI agents start at $35/month; workflow steps that don’t use AI run free and unlimited. There’s a dedicated Outline integration page, and 200+ other integrations.
Choosing per job
| Claude (Outline’s built-in MCP) | Carly | |
|---|---|---|
| Search, read, and edit wiki documents | Yes (official, first-party) | Yes |
| Pushes the runbook to Slack when an incident opens | No | Yes |
| Alerts the team when a policy doc changes | No | Yes |
| Monthly stale-doc audit, unattended | No | Yes |
| Self-hosted wiki support | Yes (your domain + /mcp) | Yes |
| Setup | Admin toggle + one URL (paid Claude plan) | Guided conversation |
| Pricing | Paid Claude plan | AI agents from $35/mo |
Frequently Asked Questions
Does Claude integrate with Outline?
Yes — natively, in a sense. Outline’s official MCP server is built into every workspace (cloud and self-hosted); an admin enables it under Settings → AI, and you add https://yoursubdomain.getoutline.com/mcp to Claude as a custom connector. Paid Claude plan required.
Do I still need a community Outline MCP server?
Generally no. The first-party server made most of them redundant — at least one prominent community project has been archived in its favor. Community servers remain an option if you need a tool the official one lacks.
Does it work with self-hosted Outline?
Yes, and that’s one of its best features: the MCP endpoint is your own instance’s URL with /mcp appended, so your wiki data never routes through a third party.
Can Claude post a runbook to #incidents when an incident opens?
Not by itself — no event in Outline (or anywhere else) can start a Claude chat. Routing documents on triggers is agent work; Carly watches for the event and delivers the doc without anyone prompting.
What are the known rough edges?
OAuth tokens expire every 60 minutes, so long-running non-interactive use needs API-key auth instead. And edits made through the server carry your identity, so give Claude precise instructions before letting it restructure a collection.
More: Claude connectors · Can Claude send emails · Claude vs Carly · Claude Cowork alternatives · Claude knowledge base · Claude + Recall.ai · Claude + tl;dv · Claude + Lever
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
