Skip to content

Roadmap

conmcp is pre-1.0 and moving fast. This page is the honest state of things: what's shipped, what's being considered, and what will not happen.

v0.1 — current

Shipped and covered by tests:

  • 8 MCP tools: get_plan_overview, search_plan_pages, get_page_text, render_page, extract_tables, extract_quantities, get_takeoff_instructions, generate_takeoff_report
  • fence_takeoff MCP prompt — guided fence & gate takeoff with field-tested gotchas
  • Three trade profiles: fence (deep), sitework (starter), general
  • Strict takeoff schema (schema_version: 1) with confidence scores and needs_review flags
  • Exports: Markdown (review), CSV (pma-standalone layout), JSON (contractor-bid compatible)
  • Path sandbox (CONMCP_ALLOWED_DIRS) and append-only audit log
  • CLI companion mirroring the tools: overview, search, quantities, tables, render, instructions, report, sample, serve, version
  • Synthetic sample plan generator — the only plan PDF that ever lives in the repo
  • CI across Python 3.11/3.12/3.13, this docs site on GitHub Pages

v0.2 — ideas under consideration

Not promises — ordering and scope will follow real usage. Roughly by pull strength:

  • Semantic search / embeddings — keyword search works on small sets; a 300-sheet hospital set wants "find sheets about perimeter security" to work even when the words don't match. Local embeddings, nothing uploaded.
  • Optional local vision backend (Ollama / MLX) — an opt-in mode where the server drives a local vision model itself for fully automated takeoff, no MCP client LLM required. The v0.1 "server never calls an LLM" default stays; this would be a separate, explicit mode.
  • XLSX export — formatted workbook output alongside CSV, since that's what actually gets emailed around.
  • More trade profiles — expanding sitework beyond the starter profile, plus screen walls and guardrail (both live next door to fence scope on the same sheets).
  • contractor-bid-pro Finding/evidence hooks — each line item handed off with its evidence: sheet reference, page-crop image, confidence (see Integrations).
  • PyPI release — once the schema and tool surface settle down.

Have a use case that should reorder this list? Open a discussion — especially if you estimate for a living.

Explicitly out of scope

Things conmcp will not do, so nobody has to wonder:

  • Pricing and labor — no unit costs, no crew rates, no margin math. conmcp stops at quantities; estimating math is contractor-bid's job.
  • BIM / IFC / CAD parsing — PDF plan sets only in v0.x. No Revit, no DWG.
  • Cloud upload of plan documents by the server — never. That's a security invariant, not a missing feature (see Privacy & safety).