Manifold

<p align="center"> </p>

日本語版 README

Manifold is a .NET foundation for defining an operation once and exposing it through both CLI and MCP surfaces.

The model is simple:

• Write one operation by hand
• Let the source generator emit descriptors and invokers
• Wire those generated artifacts into your CLI and/or MCP host

Manifold does not own your transport, hosting model, or product-specific runtime. It focuses on operation definition, binding, metadata, and fast dispatch.

If you want a runnable starting point, the repository includes sample hosts under `samples/`.

| Package | Purpose | | --- | --- | | Manifold | Core contracts, descriptors, attributes, and binding primitives | | Manifold.Cli | CLI runtime helpers and generated invocation | | Manifold.Generators | Source generator that emits descriptors and invokers | | Manifold.Mcp | MCP metadata and invocation helpers |

An operation is the single source of truth.

From that definition, Manifold.Generators emits:

• GeneratedOperationRegistry
• GeneratedCliInvoker
• GeneratedMcpCatalog
• GeneratedMcpInvoker

You compose those generated types into your own application.

Manifold supports two authoring styles:

1. Static method operations
2. Class-based operations implementing IOperation<TRequest, TResult>

Most consumers should not install all four packages.

Start with the core package and the generator, then add only the surfaces you actually use.

Typical combinations:

| Scenario | Packages | | --- | --- | | Define operations only | Manifold, Manifold.Generators | | CLI app | Manifold, Manifold.Generators, Manifold.Cli | | MCP host | Manifold, Manifold.Generators, Manifold.Mcp | | Both CLI and MCP | Manifold, Manifold.Generators, Manifold.Cli, Manifold.Mcp |

CLI host:

<ItemGrou