NORMOT — Israeli building norms

io.github.danvolsky-sourcePublished by GitHub account danvolsky-sourcev0.1.0Updated Nov 7, 2026

Israeli building and planning norms: permits, fire, accessibility; Hebrew text, source, citation.

VerifiedStreamable HTTPWeb executableLocation & LifestyleKnowledge & Memory

Overview

AI-generated overview

Remote MCP server for NORMOT, a database of Israeli building and planning norms, letting an assistant search norms, check what applies to a project and cite…

What you can do
  • Search and read norms: Hebrew keyword search and full norm text with source, section, dates in force and a citation line
  • Build a project profile: valid codes for uses, stages, cities, plot conditions, elements, roles and requirement areas
  • Assess a project: overview of applicable norms, paginated requirements by area, and why a single norm applies
  • Follow the permit process: stages of the Planning Administration's online system with the norms behind each step
  • Track sources: changed documents, expiring norms and latest Reshumot issues
When to use it
Useful when answering questions about Israeli building permits, planning and building law, fire safety, accessibility, protected spaces, parking or business licensing, or when checking which norms apply to a specific project profile.
Requirements
Remote Streamable HTTP endpoint with no sign-in; clients that only support stdio can bridge it with mcp-remote via npx. Norm texts are in Hebrew, so searches should be in Hebrew. No accounts, keys or environment variables are needed.
Before you install
Read-only tools, but answers are a preliminary check and not legal or engineering advice; NORMOT is not an official publication, so the official text is binding and the norm URL or citation line should be given. SII standard texts are not included. The server logs one line per call with method, tool name, client name and timing, not arguments, and inherits the public API's rate limits; copying the database or a substantial part needs agreement.

Installation

In SourceWeft

  1. Open NORMOT — Israeli building norms in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.danvolsky-source%2Fnormot/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "normot-israeli-building-norms": {
      "type": "http",
      "url": "https://mcp.normot.co.il/mcp"
    }
  }
}

README

NORMOT MCP server

A remote Model Context Protocol server for NORMOT, a database of Israeli building and planning norms: laws, regulations, ministry and agency guidelines, municipal spatial guidelines (הנחיות מרחביות) and references to SII standards. About 120,000 norms, each with a permanent URL, its source document and section, dates in force, and a record of how its text was checked against the printed source.

It lets AI assistants and agents (Claude, ChatGPT, Cursor and other MCP clients) look norms up directly and cite them.

Endpoint: https://mcp.normot.co.il/mcp (Streamable HTTP, no sign-in)

Tools

All tools are read-only.

ToolWhat it does
search_normsSearch norms by Hebrew words; norms in force first
get_normOne norm: full text, source, section, values, print check, citation line
list_profile_optionsValid codes for a project profile: uses, stages, cities, plot conditions, elements, roles, areas
project_overviewFor a project profile: how many norms apply, what needs data or a specialist, next permit actions, questions that narrow the list
project_requirementsThe norms that apply to a project, by area (fire, egress, parking…), 50 per page
check_norm_for_projectWhy one norm applies to a project, and what could change that
permit_stagesThe permit process mapped to the stages of רישוי זמין, with the norms behind each step
source_changesWhat changed in the sources: changed documents, expiring norms, latest Reshumot issues

Norm texts are in Hebrew, as in the source. NORMOT is not an official publication: the binding text is the official publication. Every result carries the norm's permanent URL and, for single norms, a ready citation line. Quoting single norms with a link is welcome; copying the database or a substantial part of it needs agreement (terms).

Connect

Claude (claude.ai, Claude Desktop): Settings → Connectors → Add custom connector → URL https://mcp.normot.co.il/mcp.

Claude Code:

sh
claude mcp add --transport http normot https://mcp.normot.co.il/mcp

Cursor / VS Code / other clients: add a remote (Streamable HTTP) server with the URL above. Clients that only support stdio can use mcp-remote:

json
{ "mcpServers": { "normot": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.normot.co.il/mcp"] } } }

How it works

The server is a thin, stateless layer over the public NORMOT read API. It holds no data of its own and inherits the API's rate limits; it clips long texts in lists and drops display-only fields so results fit an agent's context. It does not expose the site's semantic search (/api/hybrid).

It logs one line per call (method, tool name, client name, timing), never the arguments.

Develop

sh
npm installnpm run dev        # http://localhost:8787/mcpnpm test           # offline tests on fixturesnpm run smoke      # calls every tool against a running server and the live APInpm run typecheck

NORMOT_API_BASE overrides the API address (default https://normot.co.il/api).

Deployment and registry publishing: DEPLOY.md (in Russian).

Source: README.md at commit e2e891a

Tools

8

search_norms

Search norms

Search Israeli building and planning norms by Hebrew words (substring search over norm texts, sections and document titles; norms in force come first). Returns norms with their permanent URL; call get_norm for the full text and citation.

Parameterslimitqueryrequiredoffset

get_norm

Get one norm

One norm by id: full Hebrew text, applicability, source document and section, dates in force, numeric values, exceptions, how its text was checked against print (print_check), and a ready citation line (cite).

Parametersidrequired

list_profile_options

List project profile options

Valid codes for a project profile: uses, stages, cities (municipality slugs), plot conditions (sites), project elements (features), roles and requirement areas. Call before project_overview or project_requirements if unsure of a code.

Parameterswhich

project_overview

Project overview (what applies)

For a project profile (use, city, stage and optional details): how many norms apply, which depend on missing data or need a specialist, the next permit actions with their legal source, and which questions would narrow the list most. Every omitted detail keeps norms in (over-inclusive by design).

Parametersusebedscityrolesiteroomsstagetrackstatusstoreysfeaturesoccupancy+4 more

project_requirements

Project requirements

The norms that apply to a project profile, 50 per page, filterable by requirement area (e.g. fire, egress, parking, accessibility), by state and by Hebrew words. Texts are clipped; call get_norm for the full text.

Parametersquseareabedscityrolesiteroomsstagestatetrackoffset+8 more

check_norm_for_project

Why a norm applies to a project

For one norm and a project profile: does it apply, why (by use, authority, stage) and which conditions could change that.

Parametersidrequiredusebedscityrolesiteroomsstagetrackstatusstoreysfeatures+5 more

permit_stages

Building permit stages (Rishuy Zamin)

The building-permit process mapped to the stages of the Planning Administration's online system רישוי זמין, with the norms behind each step, plus how the database's texts were checked and the measured error rates. Without a phase: an overview of all phases. With a phase code: its steps and norms. The mapping is NORMOT's work, not a Planning Administration publication.

Parametersphase

source_changes

Recent source changes

What NORMOT's monitor detected in its sources (changed documents, expiring norms, latest Reshumot issues) and what was verified. With a profile, only documents relevant to that project.

Parametersusebedscityrolesiteroomsstagetrackstatusstoreysfeaturesoccupancy+4 more

Version history

1
  1. v0.1.0LatestNov 7, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.