MCP
A developer agent connects to Amy and pulls the approved model and change records.
For Developers
Software intent.
Your coding agent.
Your stack.
Amy helps your team define and review what the software should do. Your developer or coding agent uses that model to write, test and evolve a website, web application or mobile app in your own stack.
From reviewed intent to implementation
The approved model stays at the centre of the build.
Goals, records, actions, permissions and exceptions become a connected model the team can inspect. Choose the connection that gives your coding agent access to that agreed intent.
Orchestrator
A remote orchestrator connects using a pairing code from Amy. Its CLI redeems that code.
Build runner
A self-hosted runner gives your coding agent an environment to implement the model as conventional software.
Developer access
A developer agent pulls the approved model over MCP.
Create a token from Developer access in Amy. Give the endpoint and token to an MCP-capable coding agent.
Connect
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>"
- get_project
- Read the project and current editable version.
- list_versions
- List the project's sequential versions.
- get_intent
- Pull the full approved AIM tree.
- get_change_records
- Pull accepted changes, including changes after an ISO date.
- get_content
- Pull supplied screen copy and starting rows.
- get_bootstrap
- Read the developer workflow and specification location.
Change records
Every accepted model change travels with the model.
A developer agent can pull the current model, then use change records to target the conventional software that needs to move with it.
Pull
Read the approved AIM model and supplied content.
Implement and test
Your coding agent writes the software; your development workflow checks it against the model.
Evolve
Pull accepted changes, update the affected code and check that the software still matches the intent.
Build intent starters
Begin with the software your team needs.
These are example prompts to copy into a software project in Studio. Amy helps you work through the questions and shape the intent before you hand it to your coding agent.
Starter prompt · Web application
A customer service portal
Work through customer access, request ownership, status changes and the information each person can see.
Help me model a customer service portal for our own web application. Customers should submit requests and see their status. Our service team should assign owners and record responses. Ask me about roles, permissions, notifications, exceptions and the systems we need to connect. Help us review the intent before our coding agent implements it.
Starter prompt · Mobile application
A field service app
Define what technicians need on a visit, how evidence is recorded and what happens when connectivity is lost.
Help me model a mobile app for field service technicians. They need assigned visits, checklists, notes and photos, and a way to record completed work. Ask me about offline use, synchronisation, customer information, access and supervisor review. Make unresolved decisions visible so we can agree the intent before our coding agent builds the app.
Your controls
Review the intent. Own the implementation.
A shared model gives people and agents a reference they can question, correct and revisit as the software changes.
Review before handoff
Confirm the rules, responsibilities and exceptions with the people who know the work. Amy’s checks help surface gaps; the team decides what the model should say.
Choose developer access
Create a developer token for the coding agent you connect. Keep your project access and the agent’s development environment under your team’s control.
Keep release decisions
Your development workflow owns code review, testing and deployment. Check the running software against the agreed intent as part of that workflow.
The reverse path
Existing code can come back into the model.
Import an existing codebase or AIM tree. The Encoder recovers an intent model for you to read and confirm.
Apps & Processes
Work can also run directly in Space.
Apps and processes in Space use Amy’s shared runtime, supported capabilities and Space interface. They can put reviewed intent to work without a separate application codebase. Developer handoff gives you another path: software your team builds and operates in its own stack.
Code when you need it