Skip to main content
Glama

BOQ MCP Server

Let Claude fill data into your BOQ / Tendix projects in plain language — create projects, chapters, sections, items, quantity calculations, contractors, contracts, bills, and pricing. It talks to the BOQ REST API, so all your permissions, subscription, and audit rules stay enforced. You only see and touch the data your account is allowed to.

Install in one step

Claude Code

Just tell Claude:

Install the MCP server from https://github.com/jehadbaniodeh/boq-mcp

Claude will run the registration for you. (Or run it yourself:)

claude mcp add boq -- uvx --from git+https://github.com/jehadbaniodeh/boq-mcp boq-mcp

Claude Desktop

Settings → Developer → Edit Config, then add:

{
  "mcpServers": {
    "boq": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/jehadbaniodeh/boq-mcp", "boq-mcp"]
    }
  }
}

Restart Claude Desktop. Done.

Related MCP server: QC Database MCP Server

First use

In any chat, log in once with your BOQ account:

Log in to BOQ as me@example.com

Then talk to it naturally:

Create a project "Villa A" with a Concrete chapter (code 03), a Foundations section (code 10), and an item "Reinforced concrete C30" in m3 at 250/unit.

If your account lacks a permission, Claude is told exactly why (e.g. a 403), so it can explain it instead of silently failing.

Requirements

  • uv installed (provides uvx). One-time: curl -LsSf https://astral.sh/uv/install.sh | sh uvx then downloads and runs the server automatically — no manual clone or pip install.

  • A BOQ account on https://boq.jehadbim.com.

By default the server targets https://boq.jehadbim.com. To point at a different instance, set BOQ_API_URL in the server's env block.

Tools

Area

Tools

Auth / read

login, whoami, list_projects, get_project_tree, list_chapters, list_sections, list_items

BOQ hierarchy

create_project, update_project, create_chapter, create_section, create_item, bulk_create_items, add_calculation_line

Commercial

create_contractor, create_contract, create_bill

Pricing

add_material_cost, get_pricing_breakdown

Notes

  • Chapter / section / item codes are exactly 2 digits (e.g. 03) — the full path code is composed up the tree.

  • Item units: m, m2, m3, unit, kg, ton, lm, ls, No., set.

  • Your login token lives only in memory for the running session; it is never written to disk.

License

MIT

Available Tools

19 tools
add_calculation_lineC

Add a quantity calculation line to an item (count x dim_1 x dim_2 x dim_3 - deduction).

Inputs: item_id (required), reference (required), count, dim_1, +7 more.

add_material_costC

Add a material cost line to an item's price breakdown.

Inputs: item_id (required), material_name (required), unit (required), consumption_rate, +2 more.

bulk_create_itemsA

Create many items under one section in a single call.

Each item dict needs: code (2 digits), name, unit (+ optional quantity, unit_price, description, order, notes). section_id is applied to all.

Inputs: section_id (required), items (required).

create_billB

Create a bill against a contract. bill_type: progress|final|variation|retention_release.

Inputs: contract_id (required), bill_type, notes.

create_chapterB

Create a chapter under a project. code is exactly 2 digits (e.g. '03').

Inputs: project_id (required), code (required), name (required), description, +1 more.

create_contractC

Create a contract linking a contractor to a project.

contract_type: lump_sum|unit_price|cost_plus|time_materials.

Inputs: project_id (required), contractor_id (required), contract_number (required), contract_type, +3 more.

create_contractorC

Create a contractor. name_en required. contractor_type: main|sub|supplier|consultant.

Inputs: name_en (required), contractor_type, classification, name_ar, +3 more.

create_itemB

Create a BOQ item under a section.

code is exactly 2 digits (e.g. '01') — the full path code is composed up the chapter/section/item tree. unit must be one of: m, m2, m3, unit, kg, ton, lm, ls, No., set.

Inputs: section_id (required), code (required), name (required), unit (required), +5 more.

create_projectC

Create a new project. Only name is required.

status: draft|active|on_hold|completed|cancelled. currency: ILS|USD|EUR|JOD|SAR.

Inputs: name (required), description, client_name, location, +4 more.

create_sectionC

Create a section under a chapter. code is exactly 2 digits (e.g. '10').

Inputs: chapter_id (required), code (required), name (required), description, +1 more.

get_pricing_breakdownB

Return the full price breakdown (materials/labor/equipment/subcontracting) for an item.

Inputs: item_id (required).

get_project_treeA

Return the full project hierarchy (chapters -> sections -> items).

Use this before adding data so you don't create duplicate chapters/sections.

Inputs: project_id (required).

list_chaptersC

List chapters of a project.

Inputs: project_id (required).

list_itemsC

List items of a section.

Inputs: section_id (required).

list_projectsA

List all projects visible to the authenticated user.

Inputs: no named parameters.

list_sectionsC

List sections of a chapter.

Inputs: chapter_id (required).

loginA

Authenticate against the BOQ backend and store the JWT for this session.

Must be called before any other tool unless BOQ_API_TOKEN was provided.

Inputs: email (required), password (required).

update_projectB

Update a project. Pass only the fields you want to change.

status: draft|active|on_hold|completed|cancelled. currency: ILS|USD|EUR|JOD|SAR.

Inputs: project_id (required), name, description, client_name, +6 more.

whoamiA

Return the currently authenticated user's profile.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool maps to a distinct resource/action: auth, hierarchical reads, creation, pricing costs, and contract/bill creation are clearly separated. The list_* and get_* read tools are distinguishable by level/aggregation, and create_* tools differ by target entity. No two tools appear to do the same job.

    Naming Consistency4/5

    Almost all tools follow snake_case verb_noun conventions: list_projects, create_chapter, bulk_create_items, add_material_cost. Minor inconsistencies are login/whoami as standalone verbs and the mix of list_* for collections versus get_* for aggregate/singular reads, but the overall pattern is predictable.

    Tool Count3/5

    19 tools is in the 16-25 range that feels heavy, though the BOQ domain spans hierarchy, pricing, and contracts so each tool has a distinct role. It is not egregiously over-scoped but exceeds the ideal 3-15 range for tight coherence.

    Completeness2/5

    The hierarchy has create/read coverage, but chapters/sections/items lack update/delete, and contractors/contracts/bills are write-only with no list/get tools. Pricing breakdown mentions labor/equipment/subcontracting, yet only material costs can be added. These gaps create dead ends for agents trying to verify or maintain created data.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Autodesk Construction Cloud projects through natural language, connecting APS APIs for querying project data and issues.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to search and manage construction project economic data, including unit price analyses, resource catalogs, budget trees, and price lists, with secure multi-tenant access.
      MIT