Build a CodeModeKit Server

Build a walking skeleton for the user's actual source, then verify it through the downstream MCP surface. Keep model-authored code in CodeModeKit's sandbox and host integrations behind tool providers.

Build workflow

1. Inspect the repository, package manager, local instructions, existing MCP configuration, and relevant application functions. Do not overwrite unrelated work.
2. Choose the source boundary:
   • Use Local Tools for functions or APIs the application owns.
   • Use mcp.stdio for a shell-free executable and argument array.
   • Use mcp.http for a Streamable HTTP MCP endpoint.
   • Compose sources when one authored program needs more than one namespace.
3. For a new project, prefer the generator. Read references/generator.md for commands and generated-file ownership.
4. For a retrofit or custom server, read references/server-api.md, preserve the batteries-included facade, and expose compiler or sandbox configuration only when the user needs an expert override.
5. Define an explicit tool policy. Read references/policy-and-security.md before enabling writes, handling credentials, or binding Streamable HTTP beyond loopback.
6. Keep the initial implementation compact. A single src/server.mjs is the default; split it only when domain code already has a natural module boundary.
7. If the project includes an Agent Plugin, run catalog sync and build, but do not pretend the generated runtime skill understands the domain. Invoke $author-codemode-skill after the server works.
8. Verify the downstream behavior using references/verification.md. Exercise run_typescript, not merely imports or direct provider functions.