Skip to content
Metapad logo

Metapad

Stores an organisation's processes as a typed, multi-user knowledge graph that teams edit collaboratively and simulate, queryable over REST API or MCP.

At a glanceswept 2026-10-12

47 linking domains

Emerging

For
enterprise teams who want to model how their business works and query it with AI
Price
Price not read
Activity
Activity not read yet
Company
Domain since 2024domain registered
Runs as
API
What people do with it
  • simulate policy changes and org redesigns before rolling them out
  • publish a model as a website or multilingual PDF report
  • let Claude or other AI tools query a typed model via MCP
The companyeach fact with its source · read 2026-10-12
  • Domain since2024domain registered
Your datawhat they publish, each line with its page · read 2026-10-12

    These are Metapad's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.

    How a program reaches itfound, not claimed · read 2026-10-12
    • MCP docsmetapad.ai/en/docs/ai-assistant/using-metapad-via-mcp-claude-desktop-claude-codethe vendor's page ↗

    Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

    Alternatives in Knowledgeby use, among tools still maintained

    Figure and bar: visits/mo, estimate · year: online since

    All Knowledge tools →

    Questions this page answers
    • What is Metapad?

      Stores an organisation's processes as a typed, multi-user knowledge graph that teams edit collaboratively and simulate, queryable over REST API or MCP. It is listed in the Atlas under Knowledge.

    • Who is Metapad for?

      enterprise teams who want to model how their business works and query it with AI

    • Do people use Metapad?

      Emerging.

    • What are alternatives to Metapad?

      In Knowledge, by use: Stashr, Physea Labs, memsprout, Stipp, docbin, emdly.

    Not quite it? Describe the job

    beta

    Five tools from the Atlas that fit it, each judged against what you wrote.

    How we read a tool

    No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

    • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
    • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
    • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
    • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

    How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.