MCP
A developer agent connects to Amy and pulls the approved model and change records.
The code path
Running the model directly is the main path. When you need code, a developer agent can pull the model and its change records, then build in your stack.
One model, three connections
The connection changes. The source does not.
A developer agent connects to Amy and pulls the approved model and change records.
A remote orchestrator pairs with a code Amy generates. Its CLI redeems that code.
A self-hosted runner can implement the model as conventional software.
Developer access
Create a token from Developer access in Amy. Give the endpoint and token to an MCP-capable coding agent.
The Share panel gives you a ready-to-paste command. The token is shown once.
claude mcp add --transport http amy "https://amybuilds.com/mcp" --header "Authorization: Bearer <TOKEN>"
Change records
A developer agent can pull the current model, then use change records to target the conventional software that needs to move with it.
Read the approved AIM model and supplied content.
Generate and run conventional software from that model.
Pull later change records and update the affected realization.
The reverse path
Import an existing codebase or AIM tree. The Encoder recovers an intent model for you to read and confirm.
Code when you need it