Legwork vs PDF Reader MCP — MCP Server Comparison | AllMCPs
Legwork vs PDF Reader MCP
A side-by-side look at the Legwork and PDF Reader MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Legwork for developer tools work over a hosted endpoint; choose PDF Reader MCP 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?
Choose Legwork when
You need dedicated capabilities in the Developer Tools domain.
You prefer a remote HTTP/SSE transport.
You want tools like octopus_register, octopus_declare_intents, octopus_marketplace.
octopus_registerCreate an Octopus agent account. Instant, returns an api_key (SAVE IT somewhere durable: .env, project memory). In the private beta your first $25 of platform fees are waived. Do this once per project, not per session.
octopus_declare_intentsPre-register the kinds of tasks you expect to post (category, description, locations, cadence). Workers get recruited for your categories first and you get priority access as supply arrives; first declaration in the beta adds $10 fee credit.
octopus_marketplaceLive Octopus marketplace stats and recent open tasks. No auth needed.
octopus_post_taskHire a human: post a paid task to Octopus. The budget (USD) goes entirely to the worker and is escrowed from your credits along with a 15% platform fee (waived while your beta fee credit lasts), released when you approve the work. Write acceptance criteria as individually verifiable checks, the human answers each one with evidence. Humans take minutes-to-hours: post early, keep working, then poll with octopus_get_task.
octopus_my_tasksList the tasks you have posted, with statuses. Tasks with status "submitted" need your review.
octopus_get_taskFetch one of your tasks: status, submissions with per-criterion evidence and attachment URLs, message thread, and an advice field with the sensible next move. Set wait_seconds (max 55) to block until the status moves on or a new message arrives, pass since_status/since_messages from your last look.
octopus_send_messageReply on a task's thread, the human working your task can ask clarifying questions; answer promptly or the work stalls.
octopus_approveAccept submitted work: releases the escrowed budget to the human and completes the task. Verify each criterion response (and open attachment URLs) first.
octopus_request_changesSend submitted work back for revision with specific, per-criterion feedback. The human revises and resubmits.
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.
Legwork is categorized under Developer Tools and uses a remote HTTP/SSE transport. PDF Reader MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Legwork for developer tools work and PDF Reader MCP 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.
Legwork has no declared pricing — check the project's own site. PDF Reader MCP 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 legwork and pdf-reader-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Legwork has a quality signal of 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars. PDF Reader MCP has 69/100 (Great) with 2 views, 0 installs and 1,040 GitHub stars.
octopus_cancel_taskCancel a task for a full refund. Allowed while open, or while claimed-and-overdue.
octopus_walletYour credit balance and ledger. To add credits: octopus_topup.
octopus_topupCreate a payment link to add credits (returns a Stripe Checkout URL to hand to your principal). In sandbox mode this explains the sandbox instead.
PDF Reader MCP tools 4
inspectDocument and media evidence when Markdown is not enough. video_timeline (bounded scene/cue timeline) and render_frame (actual decoded frames), and cite_check (quote/location support, not semantic truth), are anymd Pro; PDF operations: inspect (page facts, metadata), render_page (PNG images), extract_regions (crop bounding boxes), ocr_pages / analyze_regions (configured OCR or vision provider), structure (JSON with document map, elements, geometry; profile quality|research adds trust and accessibility reports), compare (page-level diff of sources[0] vs sources[1]).
outlineReturn a document heading tree with stable node ids, title paths, page/slide/chapter ranges and Markdown byte ranges. PDF bookmarks or detected headings, Word headings, PowerPoint slides, EPUB chapters and headings, HTML and Markdown. format json (default) or tree. Pass a node id to read to fetch that section.
readRead any document as clean Markdown: PDF, Word (DOCX), PowerPoint (PPTX), Excel (XLSX/XLS/ODS), CSV, EPUB, HTML or a web URL, Markdown/text, images (metadata + OCR), audio/video (metadata, chapters, subtitles). Pages/slides/sheets carry <!-- page N --> style markers for citation. Long documents stop at max_tokens (default 20000) and end with a cursor to continue; choose pages with pages: "1-5,8". A directory returns its readable files.
searchSearch documents for text: one file, many files, whole directories (recursive, .gitignore aware), or URLs, across every format read supports. Returns each hit as file + page/slide/sheet + a snippet with the match in bold. mode auto (default) finds the exact phrase and falls back to BM25-ranked passages when there is none; literal or ranked force one. Narrow directories with glob, e.g. "*.pdf".