'%20d='M64%205c-3%2018-15%2026-13%2043-9-5-13-13-13-22C20%2043%2015%2062%2022%2082c7%2022%2023%2037%2042%2041%2022-4%2039-21%2043-43%203-17-3-32-18-45%202%2011%200%2018-6%2025C84%2036%2075%2019%2064%205Z'%20/%3e%3cpath%20fill='url(%23heat)'%20d='M64%2045c-2%2015-14%2022-13%2038-5-4-8-9-9-15-7%2010-8%2020-4%2030%205%2012%2014%2020%2026%2023%2013-3%2023-12%2027-25%203-11%200-20-8-29%200%207-2%2012-6%2016%201-16-5-27-13-38Z'%20/%3e%3c!--%20The%20glasses%20render%20as%20two%20stacked%20stroke%20groups:%20a%20pale%20warm%20casing%20under%20a%20dark%20warm-charcoal%20stroke.%20The%20casing%20keeps%20the%20dark%20strokes%20legible%20where%20they%20leave%20the%20flame%20body%20(temple%20tips,%20lower%20rims)%20on%20dark%20backgrounds,%20and%20reads%20as%20a%20rim%20light%20against%20the%20flame%20on%20light%20ones.%20--%3e%3cg%20fill='none'%20stroke='%23ffe3ae'%20stroke-opacity='0.85'%20stroke-linecap='round'%20stroke-linejoin='round'%3e%3cpath%20stroke-width='14'%20d='M7%2063c12-4%2027-5%2043-1M78%2062c16-4%2031-3%2043%201'/%3e%3crect%20x='12'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='14'/%3e%3crect%20x='70'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='14'/%3e%3cpath%20stroke-width='13'%20d='M57%2066c5-4%209-4%2014%200'/%3e%3c/g%3e%3cg%20fill='none'%20stroke='%2333221b'%20stroke-linecap='round'%20stroke-linejoin='round'%3e%3cpath%20stroke-width='8'%20d='M7%2063c12-4%2027-5%2043-1M78%2062c16-4%2031-3%2043%201'/%3e%3crect%20x='12'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='8'/%3e%3crect%20x='70'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='8'/%3e%3cpath%20stroke-width='7'%20d='M57%2066c5-4%209-4%2014%200'/%3e%3c/g%3e%3c/svg%3e){kind=small}
Tooling · 0.42.4
Build the application. Inspect the workspace. Operate the correct surface.
This section covers systems for developers and coding agents. It also explains the runtime surfaces that application agents use. These surfaces are not interchangeable. Every claim in this section was verified against the released 0.42.4 packages.Three audiences
Developers create projects, change models, generate artifacts, run tests, and apply migrations. CI runs the same project checks and generation commands. These actions can write files or change the configured development database.
Coding agents inspect source, manifests, package contracts, and generated knowledge. Development MCP is read-only. Any separate permission to edit the repository comes from the coding-agent client.
Application agents use generated local MCP, hosted application MCP, or WebMCP. Their calls can operate live data and remain inside the application authentication, tenant, permission, and field-policy boundaries.
Separate surfaces
| Surface | Primary audience | Boundary | Reach for it when |
|---|---|---|---|
| CLI, templates, and scanner | Developers and CI | Runs in the local workspace. Commands can create files, generate artifacts, inspect manifests, and apply migrations to the configured database. | You need to start an app, change its model, generate interfaces, verify it, or operate its development database. |
| Knowledge commands | Developers and coding agents | Reads workspace files, generated knowledge, installed-package contracts, and git history. It does not inspect live application data. | You need a deterministic index, freshness result, change report, or review and architecture context. |
| Development MCP | Coding agents | Runs as a local, read-only stdio server. It inspects the workspace and installed packages but cannot access the running application. | A coding agent needs structured discovery, diagnostics, generation output, or review context through MCP. |
| Generated local MCP | Local application agents | Runs beside the application and operates live data. It gets credentials from its environment and has no per-request principal, so it stays local. | A trusted application agent on the same machine must use generated model operations. |
| Hosted application MCP | Remote application agents | Runs as a stateless HTTP route. A gateway terminates authorization, and the application resolves a principal for each request. | A remote application agent needs permitted operations against a deployed application. |
| WebMCP | Browser-session application agents | Registers tools in the browser page and calls the generated REST surface as the signed-in page user. It is not a separate server. | An application agent in the browser must use actions that the current page exposes. |
| Agent Plugin | Coding-agent clients | Packages the same local Development MCP server with manifests, schemas, and skills. The client keeps credentials outside the package. | A compatible coding-agent client can discover the development integration from a package. |
Pages in this section
This page connects the tools a developer uses from the first scaffold through model changes, tests, migrations, and local operation.
→Knowledge toolingThese commands answer "what is actually in this repository, and is the written description of it still true?" They compute the answer from the workspace rather than asking a model.
→smrt-dev-mcpThis read-only server helps a coding agent understand your codebase. It returns generated source as output but never writes it. It cannot touch your running application, its data, or its users.
→Generated and app MCPThese surfaces let an application agent operate real data. Local stdio gets credentials from its environment. Hosted MCP resolves a principal per request. WebMCP uses the signed-in browser session.
→Agent Plugin packagingA compatible coding-agent client can read two small manifests instead of a configuration file. The manifests identify the local server launcher and the bundled skill location.
→Compatibility and operationsThis page records the framework promises for protocol behavior and migration compatibility. It also lists the first checks for an unresponsive server.
→