mcpField
D
DocDeploy

DocDeploy

Remote
docdeploy.ioMemory & Knowledge0Updated 28w ago

About DocDeploy

DocDeploy converts uploaded documents into indexed Markdown and provides tenant-specific MCP servers for AI agents to search, browse, and read them. Its document pipeline supports varied file formats and section-level retrieval.

Key features

  1. 01Convert documents into structured Markdown
  2. 02Process office, web, and data formats
  3. 03Index sections with navigation markers
  4. 04Search, browse, and read documents
  5. 05Tenant-specific MCP tools

Use cases

  1. 01Make manuals and PDFs searchable by agents
  2. 02Retrieve a specific document section
  3. 03Browse an organization's indexed documents

MCP support

Each tenant receives an MCP server with tools to inspect the document manifest, search, list documents, and retrieve full documents or sections.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.docdeploy.io/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

DocDeploy

Enterprise document intelligence platform. Upload docs, PDFs, manuals, and notes — DocDeploy converts them to indexed Markdown and serves them via per-tenant MCP servers so AI agents can query your knowledge base.

How It Works

Upload → Convert to Markdown → Inject Section Markers → Index → Serve via MCP
  1. Upload any document (PDF, DOCX, PPTX, XLSX, HTML, TXT, CSV, JSON, XML)
  2. Convert to clean, structured Markdown with images preserved
  3. Index sections with navigational markers and full-text search
  4. Connect AI agents via MCP — they can search, browse, and read your docs

Architecture

┌─────────────────────────────────────────┐
│  apps/app        Next.js dashboard      │  ← Vercel
│  apps/web        Marketing site         │  ← Vercel
├─────────────────────────────────────────┤
│  packages/lib         Converter pipeline│
│  packages/db          Drizzle + Neon    │
│  packages/workers     Background jobs   │  ← Render
│  packages/mcp-server  MCP per tenant    │  ← Render
└─────────────────────────────────────────┘

Tech Stack

LayerTechnology
FrontendNext.js 16, Tailwind CSS, Clerk Auth
DatabasePostgreSQL (Neon), Drizzle ORM
StorageCloudflare R2
Queuepg-boss
MCP@modelcontextprotocol/sdk (Streamable HTTP)
HostingVercel (frontend), Render (workers + MCP)

MCP Tools

Each tenant's MCP server exposes 5 tools:

ToolDescription
get_manifestFull document index — start here
search_documentsFull-text search across all docs and sections
get_documentLoad a full document with section markers
get_sectionLoad a specific section by marker
list_documentsList all available documents

Document Processing Pipeline

  • PDF — pdf-parse v2 with structure inference (chapters, numbered sections, all-caps headings)
  • DOCX — mammoth with image extraction to R2
  • PPTX — adm-zip XML parsing with slide image extraction
  • XLSX — SheetJS with multi-sheet markdown table output
  • HTML — Turndown with table preservation and nav/footer stripping
  • CSV/TSV — SheetJS for robust quoted field handling
  • TXT — Structure inference for unstructured text
  • JSON/XML — Formatted code block wrapping

Monorepo Structure

docdeploy/
├── apps/
│   ├── app/              # Dashboard (Next.js)
│   └── web/              # Marketing site (Next.js)
├── packages/
│   ├── db/               # Schema + Drizzle config
│   ├── lib/              # Converter, markers, R2, token counter
│   ├── mcp-server/       # MCP server (stdio + HTTP)
│   └── workers/          # Background document processor
├── render.yaml           # Render blueprint
├── turbo.json            # Turborepo config
└── package.json          # Workspace root

Development

# Install dependencies
npm install

# Run the dashboard locally
npm run dev:app

# Run the marketing site
npm run dev:web

Environment Variables

See .env.example for the full list. Required:

  • DATABASE_URL — Neon PostgreSQL connection string
  • NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY / CLERK_SECRET_KEY — Clerk auth
  • R2_ACCOUNT_ID / R2_ACCESS_KEY_ID / R2_SECRET_ACCESS_KEY — Cloudflare R2
  • R2_BUCKET_NAME / R2_PUBLIC_URL — R2 bucket config
  • MCP_API_KEY — Per-tenant MCP server auth (Render only)

License

Proprietary — Copyright (c) 2026 MR Dula Enterprise, LLC. All rights reserved.

Contact: [email protected]

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.