2
Add `get_attachment` MCP tool for downloading attachment content
Source: outline/outline#12314 · opened by @kbjor
Problem
When an MCP client reads a document via the fetch tool, image references in the markdown point to /api/attachments.redirect?id=<uuid>. MCP clients cannot follow these URLs because they require HTTP authentication (session cookie or API key) that is separate from the MCP connection's auth context.
This means AI assistants can read document text but cannot see any images or file attachments.
Proposed solution
Add a get_attachment MCP tool that takes an attachment ID and returns the file content (or a signed download URL) through the already-authenticated MCP session, respecting per-user and per-document access controls.
When an MCP client reads a document via the fetch tool, image references in the markdown point to /api/attachments.redirect?id=<uuid>. MCP clients cannot follow these URLs because they require HTTP authentication (session cookie or API key) that is separate from the MCP connection's auth context.
This means AI assistants can read document text but cannot see any images or file attachments.
Proposed solution
Add a get_attachment MCP tool that takes an attachment ID and returns the file content (or a signed download URL) through the already-authenticated MCP session, respecting per-user and per-document access controls.
No pledges yet. Be the first to back this.
Comments
Similar requests
Add admin controls for MCP tools when using OAuth
3 votes · 0 comments
MCP — support end-to-end attachment upload (not just presign) so clients don't need a separate API key
1 vote · 0 comments
A batch moving mcp tool
1 vote · 0 comments
Feature Request: Support @user mentions and integration mentions when creating/updating documents via MCP
1 vote · 0 comments
MCP: Support creating comments anchored to text in a document
3 votes · 0 comments
No comments yet.