Next AI Draw IO vs Paperless Ngx

A side-by-side look at the Next AI Draw IO and Paperless Ngx MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Next AI Draw IO logoNext AI Draw IODeveloper Tools · Local subprocess (stdio)Draw and edit draw.io diagrams by chatting with an AI. Web app, desktop app, and an MCP server for Claude Code, Cursor, Codex and VS Code.73GreatAuth: api key requiredPaperless Ngx logoPaperless NgxDeveloper Tools · Local subprocess (stdio)Full Paperless-ngx API for AI assistants: search, tag, edit and upload documents, workflows and more65GreatAuth: not declared

Verdict: choose Next AI Draw IO for developer tools work as a local process; choose Paperless Ngx for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Next AI Draw IO logoChoose Next AI Draw IO when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You want tools like get_drawing_guide, get_shape_library, start_session.
Explore Next AI Draw IO

Paperless Ngx logoChoose Paperless Ngx when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: PAPERLESS_URL, PAPERLESS_API_KEY.
  • You want tools like edit_documents_bulk, post_document, list_documents.
Explore Paperless Ngx

Feature & specification comparison

Rows where the two servers differ are marked.

SpecNext AI Draw IO logoNext AI Draw IOPaperless Ngx logoPaperless Ngx
CategoryDeveloper ToolsDeveloper Tools
Quality signal73/100 · Great65/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNot declared
PricingBYOK (pay the provider)Not declared
Required env varsNone listedPAPERLESS_URLPAPERLESS_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars36,40311
Directory activity 7 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools16109

Tools & capabilities

Next AI Draw IO tools 16

  • get_drawing_guideReturn the drawing guide: XML format, layout, edge routing, style and editing rules. start_session already returns it; call this only if the guide is no longer in your context. With topic, returns a short XML reference for tables, layers or groups.
  • get_shape_libraryGet the style syntax and shape names of a draw.io icon library. Call this BEFORE drawing with cloud, network or other icon shapes, and use the exact names it returns; never guess them. Libraries: - Cloud: aws4, azure2, gcp2, alibaba_cloud, openstack, salesforce - Networking: cisco19, network, kubernetes, vvd, rack - Business: bpmn, lean_mapping - General: flowchart, basic, arrows2, infographic, sitemap - UI/Mockups: android, material_design - Enterprise: citrix, sap, mscae, atlassian - Engineering: fluidpower, electrical, pid, cabinets, floorplan - Icons: webicons
  • start_sessionStart a new diagram session, or continue a saved one with session_id, and open the browser for real-time preview. Starts an embedded server and opens a browser window with draw.io. The browser will show diagram updates as they happen. The result includes the drawing guide; follow it when drawing.
  • list_saved_diagramsList the diagrams saved by earlier sessions (auto-save files), newest first, with their pages. Continue one with start_session session_id=<id>; the file path also works with load_diagram.
  • create_new_diagramCreate a NEW diagram, REPLACING the whole document: every page and any unsaved user changes (the previous state stays in History). To add a tab use add_page; to change cells use edit_diagram. Before using icon shapes (AWS, Azure, GCP, Kubernetes, Cisco...), call get_shape_library first. Follow the drawing guide returned by start_session (call get_drawing_guide if it is no longer in your context). Pass screenshot: true on the last call of a complex diagram to check the result. Accepted xml: 1) Only the mxCell elements of one page (recommended). The server adds <mxfile>, <mxGraphModel>, <root> and the root cells "0" and "1": <mxCell id="2" value="Shape" style="rounded=1;" x="40" y="40" w="120" h="60"/> 2) A bare <mxGraphModel> with <root> (one page). 3) A full <mxfile> with one or more <diagram> pages. Every page's <root> must start with <mxCell id="0"/><mxCell id="1" parent="0"/>. Rules: cells are siblings (never nested), ids are unique per page and start from "2", parent only for shapes inside a container, no XML comments, and shapes stay within x 0 to 800 and y 0 to 600. A style used by several cells is defined once with <mxStyle name="..." value="..."/> before the cells and used by name (see the drawing guide); html=1 and whiteSpace=wrap are added automatically. To clear the canvas to one blank page, send only the two root cells <mxCell id="0"/><mxCell id="1" parent="0"/>; the previous diagram stays in History.
  • load_diagramLoad a .drawio diagram into the current session, REPLACING the entire diagram (all pages). To change an existing file, load it here, edit with edit_diagram, then export_diagram to the same path; never rewrite the file by hand. Provide ONE of two mutually exclusive sources: 'path' (the server reads the file from disk — you do NOT need to read the file yourself or pass its XML through create_new_diagram) or 'xml' (the raw file content you already have — from another tool, a repository read, or an API response — so no temporary file needs to be written first). Both accept plain XML and draw.io's compressed save format. .drawio.svg (Editable SVG, the format export_diagram writes) is accepted too; .png files (also draw.io's editable PNG) and plain .svg files cannot be loaded. After loading from 'path' (or from compressed 'xml'), call get_diagram before edit_diagram — you haven't seen the file's cell IDs yet. Plain-XML 'xml' content you supplied yourself is already known and can be edited immediately.
  • edit_diagramEdit a specific page in the current diagram by ID-based operations (update/add/delete cells). All-or-nothing: if any operation fails, nothing is applied and every failure is listed. Freshness: the server remembers the last diagram state you have seen, and rejects this call only if the user edited the diagram in the browser since then. You do NOT need to call get_diagram before every edit: a rejected call changes nothing and includes the current XML of the page, so you can rebuild your operations and retry. Call get_diagram first only when you don't know the current diagram content (cell IDs, structure) — e.g. the diagram wasn't created in this conversation, or you're unsure your memory of it is accurate. Multi-page targeting: - page_id / page_name / page_index are optional; when all omitted, the FIRST page is targeted - Use list_pages to discover what pages exist Operations: - add: Add a new cell. Provide cell_id (new unique id within the page) and new_xml. One cell per operation. - update: Replace an existing cell by its id. Provide cell_id and complete new_xml. - delete: Remove a cell by its id. Only cell_id is needed. Its children and connected edges are deleted too, so give only a container's id. For add/update, new_xml is the complete mxCell (inside its <object> wrapper when it has custom data, see the drawing guide) in the compact form (a shape with x, y, w, h; an edge with source and target). No XML comments. Every " inside new_xml must be escaped as \" in the JSON. Example - Add a rectangle on the default (first) page: {"operations": [{"operation": "add", "cell_id": "rect-1", "new_xml": "<mxCell id=\"rect-1\" value=\"Hello\" style=\"rounded=1;\" x=\"100\" y=\"100\" w=\"120\" h=\"60\"/>"}]} Example - Delete a cell on the default page: {"operations": [{"operation": "delete", "cell_id": "rect-1"}]}
  • get_diagramGet the current diagram XML (fetches latest from browser, including user's manual edits). Call this when you don't know the current diagram content (cell IDs, pages, structure) — e.g. before editing a diagram you didn't create in this conversation, or after edit_diagram was rejected because the user changed the diagram in the browser. Returns the full <mxfile> by default. If a page selector is provided, returns just that page's <mxGraphModel> embedded in a one-page <mxfile> wrapper.
  • get_selectionReturn the cells the user has selected in the preview: their ids and labels, for edges the source and target ids, for shapes the position and size, and the page they are on. Call this when the user refers to what they selected ("this box", "these arrows", "the selected shapes"), then act on the ids with edit_diagram. Says when nothing is selected. Needs the preview tab to be open.
  • screenshot_diagramRender the diagram in the preview and return it as a PNG image, so you can see your own result. Call this once after drawing or heavily editing a complex diagram, then fix overlaps and edges that cross shapes. Without a page selector it shows the page on screen; with one it renders that page without changing what the user sees. Needs the preview tab to be open.
  • export_diagramExport the current diagram to a file. Supports .drawio (XML), .png, .svg, and .drawio.svg (an SVG with the diagram embedded, which draw.io and load_diagram can open again). The format is auto-detected from the file extension, or can be specified explicitly. Images get a 20 px margin; a PNG has a white background (or the page's own background color) unless transparent is true. Multi-page behaviour: - .drawio with NO page selector: writes the full <mxfile> (all pages). - .drawio with a page selector: writes a single-page <mxfile> containing only that page. - .png / .svg with NO page selector: exports the currently active page in the browser. - .png with a page selector: renders that page without changing what the user sees. - .svg / .drawio.svg with a page selector: temporarily loads that page into the browser, captures it, then restores the full document (the user sees a brief flicker).
  • list_pagesList every page (tab) in the current diagram. Returns each page's id, name, 0-based index, and cell count. Use this to discover what pages exist before targeting one with edit_diagram, get_diagram, export_diagram, rename_page, or delete_page.
  • +4 more on the listing page

Paperless Ngx tools 109

  • edit_documents_bulkApply ONE of a fixed set of operations to MANY documents at once. Methods: set_correspondent, set_document_type, set_storage_path, add_tag, remove_tag, modify_tags, modify_custom_fields, set_permissions, delete, reprocess, merge, split, rotate, delete_pages, edit_pdf, remove_password. For per-document field edits including title, content, created (date), archive_serial_number, or owner, use update_document instead — those fields are not editable here. Note: 'remove_tag' only removes the tag from the specified documents (tag stays in the system); 'delete_tag' permanently deletes the tag from the entire system. ⚠️ WARNING: method 'delete' permanently deletes documents and requires confirm=true. Select documents either by `documents` (IDs) or by `all: true` + `filters` — Paperless document filter names such as correspondent__id, tags__id__all, document_type__id, title_content, created__date__gte or query (full text); the filter form changes every matching document in one call, e.g. reassigning all documents from a duplicate correspondent before deleting it. Unknown filter keys are refused, and the result reports matched_documents. all=true is not supported for merge, split, delete_pages, edit_pdf or remove_password. Method remove_password strips a PDF password (needs `password`); with update_document=true the unlocked file is stored as a new version of the same document. Method reprocess accepts remote_ocr=true to use the configured remote OCR engine.
  • post_documentUpload a new document file (PDF, image, etc.) to Paperless-NGX with optional metadata. Upload is asynchronous: by default returns a task UUID (use list_tasks to track consumer progress) — the actual document ID is assigned only after the consumer has processed the file. Set poll=true to wait for the consumer to finish and return the final result (the new document_id on success, or the consumer error on failure) in a single call. Optional metadata: title, created (date), correspondent, document_type, storage_path, tags, archive_serial_number, custom_fields.
  • list_documentsList and filter documents by fields such as title, correspondent, document type, tag, storage path, creation date, and more. IMPORTANT: For queries like 'the last 3 contributions' or when searching by tag, correspondent, document type, or storage path, you should FIRST look up the correct ID — get_filing_options returns every tag, correspondent, document type and storage path in one call (or use list_tags / list_correspondents / list_document_types / list_storage_paths) — and then use that ID as a filter here. Only use the 'search' argument for free-text search when no specific field applies. Using the correct ID filter will yield much more accurate results. Note: Document content is excluded from results by default. Use 'get_document_content' to retrieve content when needed. To find near-duplicates of one document use more_like_id; to list everything Paperless has flagged as a duplicate use has_duplicates=true.
  • get_documentGet a specific document by ID with full details including correspondent, document type, tags, and custom fields. Note: Document content is excluded from results by default. Use 'get_document_content' to retrieve content when needed. Documents can have several file versions (`versions`; manage them with upload_document_version / update_document_version / delete_document_version). Content (get_document_content) and get_document_metadata follow the LATEST version, but page_count, original_file_name and archived_file_name always describe the ROOT (first) version — e.g. after a password-protected PDF was unlocked into a new version, page_count stays null. Don't use page_count to judge whether a document is readable; check its content.
  • get_document_contentGet the text content of a specific document by ID. Use this when you need to read or analyze the actual document text. For long documents, read a slice with max_chars (and offset to continue) — e.g. max_chars: 2000 is usually enough to identify a document. Paperless stores the text without page boundaries, so slices are by characters, not pages.
  • search_documentsRanked full-text search through Paperless's search index (content, title and metadata). mode 'query' (default) takes advanced syntax — AND/OR/NOT, "quoted phrases", field:value, wildcards*; 'text' takes plain words with no syntax; 'title' searches titles only. The index is updated in the background and can lag behind or miss documents: if you expect matches but get none, use list_documents with `search`, which scans the database directly. For filtering by tag, correspondent, type or date use list_documents. Content is excluded from results; use get_document_content.
  • download_documentDownload a document file by ID. Returns the document as a base64-encoded resource.
  • get_document_thumbnailGet a document thumbnail (image preview) by ID. Returns the thumbnail as a base64-encoded WebP image resource.
  • update_documentUpdate fields on ONE document (PATCH — only fields you supply are changed). To change tags, prefer add_tags / remove_tags: they leave the other tags alone. `tags` REPLACES the whole list — any tag you leave out is removed. Every tag change returns tag_changes {added, removed}. Editable fields: title, correspondent, document_type, storage_path, tags, add_tags, remove_tags, content (raw searchable text), created (document date, YYYY-MM-DD), archive_serial_number, owner, custom_fields. For applying the same change to MANY documents, see edit_documents_bulk. To add a comment/annotation rather than change a field, see create_document_note.
  • email_documentSend a document via email to one or more recipients.
  • get_document_historyGet the change history / audit log for a document, showing who changed what and when.
  • get_document_previewGet a full-page preview image of a document. Returns the preview as a base64-encoded image resource.
  • +97 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Next AI Draw IO

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "next-ai-draw-io": {
      "command": "npx",
      "args": [
        "-y",
        "@next-ai-drawio/mcp-server@latest"
      ]
    }
  }
}

Paperless Ngx

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "paperless-ngx-2": {
      "command": "npx",
      "args": [
        "-y",
        "paperless-ngx-mcp"
      ],
      "env": {
        "PAPERLESS_URL": "YOUR_PAPERLESS_URL_HERE",
        "PAPERLESS_API_KEY": "YOUR_PAPERLESS_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Next AI Draw IO is categorized under Developer Tools and uses a local stdio subprocess. Paperless Ngx belongs to Developer Tools and uses a local stdio subprocess. Pick Next AI Draw IO for developer tools work and Paperless Ngx for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Next AI Draw IO is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Paperless Ngx has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add next-ai-draw-io and paperless-ngx-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Next AI Draw IO has a quality signal of 73/100 (Great) with 7 views, 0 installs and 36,403 GitHub stars. Paperless Ngx has 65/100 (Great) with 0 views, 0 installs and 11 GitHub stars.