Developer-tools MCP server
MetaEngine MCP
Version history of discovered tools, schemas, and declared agent authority.
OBSERVED INTERFACE
Capability surface
Modelara’s observed declarations are shown separately from its derived effect classifications.
- 1
- 0
- 0
- 7
Unknown means Valyd could not determine the capability's effect confidently from the declared interface and static evidence. It is not treated as safe.
- Package
- @metaengine/mcp-server@1.5.0
- Registry
- npm
- Published
- Sep 15, 2026
- Integrity
sha512-yntTRl2igzYFBe9gWKrBcjwbnL4El1OTMac0wlK2EuJnMiv+elpNm5i2pyuL9yO0WJHUa+e8vE+KqXKGrTbNRQ==- Analyzer
- modelara v0.1.8 · policy not recorded
8 capabilities
| Capability | Type | Derived effect | First observed in Valyd coverage | Last changed |
|---|---|---|---|---|
generate_codemetaengine:tool:generate_codeObserved interface and hashesGenerate source files from a structured type graph for TypeScript, Python, Go, C#, Java, Kotlin, Groovy, Scala, Swift, PHP, and Rust. Use explicit templateRefs to link target-language customCode to generated types and imports. For compact field maps and repeated patterns, use generate_from_recipe. # MetaEngine MCP — generation guide MetaEngine generates source files from structured type definitions and target-language code. Type and model generation supports TypeScript, Python, Go, C#, Java, Kotlin, Groovy, Scala, Swift, PHP, and Rust. ## Choose a tool - `generate_from_recipe`: compact property maps, explicit references, reusable parameter templates, and local JSON data rows. Start with [RECIPES.md](./RECIPES.md), also available as `metaengine://guide/recipes`. - `generate_code`: the existing complete native JSON payload. - `load_spec_from_file`: the same native payload read from a local file. - `generate_openapi`, `generate_graphql`, `generate_protobuf`, `generate_sql`: convert an existing schema using their tool-specific options. The three type-graph tools share the hosted generation API and local file writer. `dryRun` previews source without writing it; `skipExisting` defaults to true. The hosted request limit is 250 counted types, with the existing counting rule documented in the recipe guide. ## References and batch boundaries Generate related types together. IDs resolve within a single request. A class or interface declares `typeIdentifier`; a property refers to it with the same field. Recipes also accept the compact aliases `id` on definitions and `ref` on map properties. Use `templateRefs` wherever target-language text refers to an internal type: ```json { "code": "read(): Promise<$item>;", "templateRefs": [{ "placeholder": "$item", "typeIdentifier": "item" }] } ``` The reference resolves the type name and supports import generation. Merely writing an internal type's name in a raw code string does not create a graph reference. `templateRefs` are supported on custom code, native property type expressions, constructor parameter type expressions, and decorators; properties also support `commentTemplateRefs`. External types use `customImports` with the target language's import path and names. The generator handles recognized standard-library imports. It does not install external packages. Custom-file identifiers belong to import resolution, not the regular type graph. Where supported, refer to one with `customImports.path`; for C#, use the custom file's namespace. Do not target a custom-file identifier with `ref` or `templateRefs.typeIdentifier`. Code inside a custom file can still use `templateRefs` to refer to ordinary generated types. ## Declarations and custom code Use `properties` for typed declarations. Use `customCode` for methods, initialized fields, constructors with bodies, and other target-language members. Keep each member in its own code block. `customFiles` produce files without a class wrapper and can hold functions, aliases, or other source content. Use interface method signatures in `customCode` when classes will implement those methods. A function-typed property and a method are different declarations. Constructor parameters can create properties in the selected language. Do not repeat a constructor parameter as an additional property. For a constructor with custom logic, supply the constructor code and any fields explicitly in `customCode`. The generator renders your supplied structure and code. Compile the result in its real project to check method bodies, dependencies, language rules, and compiler options. ## Native features retained by recipes | Feature | Native fields | | --- | --- | | Named types | `classes`, `interfaces`, `enums`, `typeIdentifier`, `name`, `path`, `fileName` | | Properties | `name`, `primitiveType`, `typeIdentifier`, `type`, `isOptional`, `isInitializer`, comments and decorators | | Inheritance | `baseClassTypeIdentifier`, `interfaceTypeIdentifiers` | | Generic definitions | `genericArguments` with name, constraint, and optional property metadata | | Concrete generic references | `concreteGenericClasses`, `concreteGenericInterfaces`, `identifier`, `genericClassIdentifier`, `genericArguments` | | Collection references | `arrayTypes`, `dictionaryTypes` | | Target-language content | `customCode`, `customFiles`, `customImports`, `templateRefs` | | Generation settings | `initialize`, `packageName`, `typeScriptOptions`, `skipEnumMembersValidation` | Array, dictionary, and concrete generic definitions are virtual types: they can be referenced but do not generate files of their own. A concrete generic's `genericClassIdentifier` refers to its generic declaration, including for interfaces; keep that existing field name. ## Language notes ### TypeScript For Node16/NodeNext ESM, use `typeScriptOptions: {"relativeImportExtension":"js"}` so generated `.ts` source imports runtime `.js` paths. The default uses extensionless relative imports. Native primitives `String`, `Number`, `Boolean`, `Date`, and `Any` render as `string`, `number`, `boolean`, `Date`, and `unknown`. Recipes spell those primitive choices in lowercase. For native expressions such as `Map<string, $item>`, use `type` plus `templateRefs`. The engine can normalize interface names. Use references to obtain the rendered name, and explicit `fileName` values when an interface and class would otherwise share a file name. ### C# `packageName` sets the root namespace; type paths contribute namespace segments. Omit the package name when you want no root namespace. Do not put namespace wrappers in individual custom members. `Number` selects `int`. Use native `type: "decimal"` or `type: "double"` for those numeric types. Optional properties use the language's nullable representation. Configure nullable reference types and the language version in the consuming project. Use `templateRefs` for internal cross-namespace types in custom code. For a specific collection such as `List<T>`, use `type: "List<$item>"` with a reference. The language emitter chooses the collection spelling for a virtual `arrayTypes` definition. ### Other languages Keep method bodies and native type expressions in the selected language. Python bodies need valid indentation. Go multi-file output needs a package/module layout appropriate to the consuming project. Add the generated code's required libraries to the target project. ## Before generation 1. Include every internally referenced type in the same batch. 2. Use structured properties for declarations and custom code for behavior. 3. Make every internal reference in a raw type expression or code block explicit with `templateRefs`. 4. Choose output paths, native imports, package/namespace names, and compiler options deliberately. 5. Review and compile the generated output. [Complete examples](./EXAMPLES.md) · [Recipe syntax and limits](./RECIPES.md) Input schemasha256:6698a924cf340decaf8b6a8032067f9d56babad799adecb2098993911d4ef512Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.4.1 | 1.5.0 | |
generate_from_recipemetaengine:tool:generate_from_recipeObserved interface and hashesExpand a compact, versioned JSON recipe locally into the existing generation payload, then generate through the MetaEngine API. Use field maps, explicit type references, and named templates with parameter rows to describe repeated structures. Target-language customCode and templateRefs retain the existing type graph and import resolution. Recipe expansion executes no scripts. Supply exactly one of recipe or recipeFilePath. Validation and expansion finish before any API request or generated-file write. Input schemasha256:7a376eb214c6b5906aab47f164ac527825b1c34c46caf3ce9abf0bb65e3c1237Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.5.0 | 1.5.0 | |
generate_graphqlmetaengine:tool:generate_graphqlObserved interface and hashesGenerates a fully typed HTTP client from a GraphQL SDL schema. Supports Angular, React, TypeScript Fetch, Go, Java Spring, C#, Kotlin, Python, Rust, and Swift. Enable `fragments` to emit reusable named GraphQL fragments for object-type selections. Input schemasha256:7620881e4bcd820bde33570525ae48f7e0a8f5be839c464eb211f05041504d7aOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.4.1 | No change observed | |
generate_openapimetaengine:tool:generate_openapiObserved interface and hashesGenerate HTTP clients from OpenAPI specifications for 10 frameworks: Angular, React, TypeScript Fetch, Go net/http, Java Spring, Python httpx, C# HttpClient, Kotlin Ktor, Rust Reqwest, Swift URLSession. Provide an inline OpenAPI spec (YAML/JSON) or a URL, choose a framework, and get fully typed, production-ready HTTP client code with models, services, and error handling. Input schemasha256:c4fa8c6e2f7c2a2fe55c144e646d54169e0102f4186649676d6ce6a0ec0f2a91Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.4.1 | No change observed | |
generate_protobufmetaengine:tool:generate_protobufObserved interface and hashesGenerates a fully typed HTTP client from Protocol Buffers (.proto) definitions. Supports Angular, React, TypeScript Fetch, Go, Java Spring, C#, Kotlin, Python, Rust, and Swift. Input schemasha256:4cdc30595603f1bb6ddb8a358144568f8fb897580aa04134a5f8b556afdc1c76Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.4.1 | No change observed | |
generate_sqlmetaengine:tool:generate_sqlObserved interface and hashesGenerates typed model classes from SQL DDL (CREATE TABLE statements). Supports TypeScript, C#, Go, Python, Java, Kotlin, Groovy, Scala, Swift, PHP, and Rust. Input schemasha256:63176a7346bc4157da06e04a0ca76de46d19d0f4ddd76e4d0b7977355bd6caacOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.4.1 | No change observed | |
load_spec_from_filemetaengine:tool:load_spec_from_fileObserved interface and hashesRead an existing generate_code JSON payload from a local file and run the same generation flow. Use generate_from_recipe for compact field maps and reusable JSON templates. outputPath, skipExisting, and dryRun arguments override values in the file. Input schemasha256:cdf657c280b4461e64903256ee51eb65431f33b6f793581c15dc2bcef1862b1fOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.4.1 | 1.5.0 | |
metaengine_initializemetaengine:tool:metaengine_initializeObserved interface and hashesReturns essential MetaEngine patterns and documentation resources. This helper tool provides AI assistants with critical MetaEngine concepts: - The fundamental principle of generating related types in ONE call - Properties vs customCode distinction - Template references and type referencing patterns - Language-specific best practices Returns links to comprehensive documentation with patterns and examples. Call this when you need guidance or are generating code for the first time. Input schemasha256:4685b63bfe60ada44aca277b522882bdc9eccf53870812253ab290ad6c96545dOutput schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 1.4.1 | No change observed |
No capabilities match these filters.
STATIC COMPARISONS
Release history
- 1.4.2 1.5.0FAIL1 added0 removed1 schema0 write0 destructive1 unknown
- 1.4.1 1.4.2REVIEW0 added0 removed1 schema0 write0 destructive0 unknown