metamodel

AI-callable calculators and engineering models with real formulas. No hallucinated math.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
83%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~543Tokens (tool definitions)
~670 BTypical response size
Minimal attention impact (0.42% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "metamodel": {
      "command": "npx",
      "args": [
        "metamodel-mcp"
      ]
    }
  }
}

Runnable packages

npmmetamodel-mcp1.1.2stdio

Remote endpoints

https://www.metamodel.app/api/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢metamodel_list_projects

Browse available MetaModel calculators and engineering models. Returns project names, descriptions, tokens, and model names for each published project.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢metamodel_get_schema(token)

Get the input/output schema for a published MetaModel project. Returns model names, input parameters (with types, defaults, validation), and output fields. Models marked "presentation": true are display scaffolding (3D scenes etc.) — skip them for engineering analysis. Use a token from metamodel_list_projects.

Input Schema

{
  "type": "object",
  "properties": {
    "token": {
      "type": "string",
      "description": "The publish token of the project (from metamodel_list_projects)"
    }
  },
  "required": [
    "token"
  ],
  "additionalProperties": false
}
⚪metamodel_export_kn(token)

Export a published MetaModel project as KN notation — a human-readable text spelling of the model: nested Component blocks, "Name: value" literals, "Name: expression" formulas, dotted cross-references. Deliberately lossy (rules, indicators, validations, table data and views are omitted). Useful for reading or diffing the engineering knowledge behind a project.

Input Schema

{
  "type": "object",
  "properties": {
    "token": {
      "type": "string",
      "description": "The publish token of the project (from metamodel_list_projects)"
    }
  },
  "required": [
    "token"
  ]
}
🟢metamodel_compute(token, model, inputs)

Run a computation on a MetaModel project. Send input values and get computed outputs from all models. Inputs are auto-routed to the correct model by property name. Models marked "presentation": true in results are display scaffolding, not engineering outputs. Use metamodel_get_schema first to discover available inputs and outputs.

Input Schema

{
  "type": "object",
  "properties": {
    "token": {
      "type": "string",
      "description": "The publish token of the project"
    },
    "model": {
      "type": "string",
      "description": "Target a specific model by name. When omitted, returns outputs from ALL models (recommended)."
    },
    "inputs": {
      "type": "object",
      "description": "Input values as key-value pairs (e.g., {\"width\": 12}). Auto-routed to the correct model. Omitted inputs use defaults.",
      "additionalProperties": true
    }
  },
  "required": [
    "token"
  ],
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools
verifiedversion not recorded4 tools