MetaModel MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| metamodel_list_projectsA | Browse available MetaModel calculators and engineering models. Returns project names, descriptions, tokens, and model names for each published project. |
| metamodel_get_schemaA | Get the input/output schema for a published MetaModel project. Returns model names, input parameters (with types, defaults, validation), and output fields. Use a token from metamodel_list_projects. |
| metamodel_computeA | 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. Optionally specify a single model to target. Use metamodel_get_schema first to discover available inputs and outputs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: listing projects, getting schemas, and running computations. No overlap or ambiguity.
All tools follow a consistent `metamodel_verb_noun` pattern (list_projects, get_schema, compute), making naming predictable and clear.
Three tools is ideal for this focused domain. Each tool is essential for the workflow of discovering and using MetaModel projects.
The tool surface covers the full workflow: discover projects, understand their inputs/outputs, and run computations. No obvious gaps for the stated purpose.