{ "SchemaVersion": "1", "Kind": "DirectoryIssues", "Slug": "outline-mcp-server", "Name": "Outline MCP Server", "CanonicalUrl": "https://askpod.ai/mcp/outline-mcp-server/issues", "ServerUrl": "https://askpod.ai/mcp/outline-mcp-server", "IssueTotal": 15, "Held": 15, "Issues": [ { "Title": "Official MCP", "Excerpt": "Hi 👋 – maintainer of @outline here \n\nWe now have an [official MCP server](https://docs.getoutline.com/s/guide/doc/mcp-6j9jtENNKL) built into the application as of https://github.com/outline/outline/releases/tag/v1.6.0 It includes fine-grained document patching and OAuth, so is ideal for most folks.\n\nIt would be great if you can include a notice at the top of the README to make folks aware of this – cheers!", "SourceUrl": "https://github.com/Vortiago/mcp-outline/issues/107", "PublishedAt": "2026-04-13T01:49:40.000Z", "State": "closed", "Comments": 4, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Smart Features not working in Claude Desktop", "Excerpt": "### What happened?\n\nI had follow the instructions and couldn't get it working.\n\nFew AI cycles and it implemented a fix locally:\n\n```\nThe bug: In vector-store.js, createInitRecord() (line 36-44) creates the table with only 5 fields: id, vector, text, title, url. But the actual sync records (line 96-104 in index.js) include 7 fields — adding documentId and updatedAt. When syncDocuments() first calls getDocumentIds() (line 61) before any real records are inserted, it queries for documentId and upda", "SourceUrl": "https://github.com/Vortiago/mcp-outline/issues/64", "PublishedAt": "2026-02-22T23:39:48.000Z", "State": "closed", "Comments": 2, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Parameter fields marked as required?", "Excerpt": "I can't tell if I have a genuine bug or not. Or can't figure out how I might make certain. Please excuse my ignorance on the topic of MCP internals.\n\nAre model parameters marked as required? My LLM's were doing pretty good about filling them out in the past but lately they seem to ignore the parameter field and leave it blank despite having all the information to chat back at me. Multiple models, old, new seem to be doing a lot worse. I wondered if maybe the tool descriptions have changed or g", "SourceUrl": "https://github.com/Vortiago/mcp-outline/issues/153", "PublishedAt": "2026-07-25T01:03:35.000Z", "State": "open", "Comments": 1, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Add MCP tool to list out recently documentation changes", "Excerpt": "### Describe the feature\n\n## Describe the feature\n\nMy team is using outline for documentations as well as outline MCP tools, which is great. However, it could be nicer if we have a MCP tool like `list_recent_changes` to update new document changes instead of scrolling manually\n\n## Use case\n1. User open AI Agent (Claude Code, Codex)\n2. Prompt \"What is recent docs change in this week\"\n3. User get response from AI Agent\n\nI would like to contribute this feature\n\n### Use case\n\n_No response_\n\n### Alte", "SourceUrl": "https://github.com/Vortiago/mcp-outline/issues/119", "PublishedAt": "2026-06-11T01:13:46.000Z", "State": "closed", "Comments": 1, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Ability to disable the AI Features for local instances", "Excerpt": "Would be good to be able to disable the ai tool via ENV variable.\n\nLocal/OS Installations have no AI features (for now), so often the model thinks that it can use the feature and gets errors.\n\nPrompting it to NOT use the tool doesn't work reliably.\n\nIs this an option for you? Or am i missing something?", "SourceUrl": "https://github.com/Vortiago/mcp-outline/issues/41", "PublishedAt": "2025-11-19T16:31:02.000Z", "State": "closed", "Comments": 1, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Sharing vscode continue extension and docker compose configs for tinkerers", "Excerpt": "Hello, this works well.\n\nJust wanted to share. I got this working under docker compose and then was able to connect to it in vscode using the continue extension. Here's what the two important configurations look like. Hopefully it helps speed things up for someone else.\n\n\n**Docker Compose** \n\n```yaml\nservices:\n mcp-outline:\n # Use the pre-built image or your locally built image\n image: ghcr.io/vortiago/mcp-outline:latest # Example image path\n ports:\n # Maps the container port 3", "SourceUrl": "https://github.com/Vortiago/mcp-outline/issues/27", "PublishedAt": "2025-11-10T19:52:39.000Z", "State": "open", "Comments": 1, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Can I use it in Cursor? How can I configure mcp.json??", "Excerpt": "Could you provide me the proper way to configure mcp.json to use it in Cursor?", "SourceUrl": "https://github.com/Vortiago/mcp-outline/issues/10", "PublishedAt": "2025-05-04T05:19:08.000Z", "State": "closed", "Comments": 1, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Tracking: prepare for MCP SDK v2 / the 2026-07-28 stateless spec", "Excerpt": "## Summary\n\nThe next MCP spec (dated **2026-07-28**, currently a locked Release Candidate) and the matching **Python SDK v2** introduce changes that affect mcp-outline's transport and session model. This is an umbrella tracking issue — split items into dedicated issues when implementation starts.\n\n**Timeline:** SDK v2 beta ~2026-06-30, stable ~2026-07-27. Spec finalizes 2026-07-28.\n\n## What changes (and why it matters here)\n\n1. **Stateless protocol core** — no `initialize` handshake, no `Mcp-Ses", "SourceUrl": "https://github.com/Vortiago/mcp-outline/issues/135", "PublishedAt": "2026-06-25T14:53:00.000Z", "State": "open", "Comments": 0, "Reporter": "Maintainer", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Pin `mcp` to `<2` ahead of the breaking SDK v2 release", "Excerpt": "## Summary\n\n`pyproject.toml` currently pins `mcp[cli]>=1.20.0` with **no upper bound** (lines 16 and 31). The MCP Python SDK is moving to a **v2** that aligns with the new 2026-07-28 spec (stateless protocol core — no `initialize` handshake, no `Mcp-Session-Id` header). v2 is a **breaking change**, and the SDK maintainers explicitly recommend pinning `<2` until you migrate deliberately.\n\nTimeline (per the python-sdk README): **beta targeted 2026-06-30, stable v2 2026-07-27.** v2 alphas are alrea", "SourceUrl": "https://github.com/Vortiago/mcp-outline/issues/134", "PublishedAt": "2026-06-25T14:52:45.000Z", "State": "closed", "Comments": 0, "Reporter": "Maintainer", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "support image upload inline text and image modification", "Excerpt": "### Describe the feature\n\nwould be greate if we can use the api to add attachments https://www.getoutline.com/developers#tag/attachments/post/attachmentsdelete\n\nthis seams to currently not work\n\n### Use case\n\n_No response_\n\n### Alternatives considered\n\n_No response_", "SourceUrl": "https://github.com/Vortiago/mcp-outline/issues/115", "PublishedAt": "2026-05-20T20:08:23.000Z", "State": "open", "Comments": 0, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Add Attachment fetch support", "Excerpt": "### Describe the feature\n\nProblem\nDocuments in Outline can contain attachments (PDFs, images, etc.). The MCP Outline server exposes document text but not attachment content, so agents cannot read or analyze attachments.\n\nDesired behavior\nAgents should be able to fetch and use attachment content (e.g., PDFs, images) linked in Outline documents.\n\nOutline API\nOutline already supports this via the attachments.redirect endpoint:\nEndpoint: POST /api/attachments.redirect\nInput: { \"id\": \"