Build a macro with MCP
Describe the task to your connected assistant. It can inspect your current project and create steps that you can review and edit in JAQ Macro.
Start the connection
Open Account → MCP and check your access and device status. Use Copy AI quick start to configure a trusted client that supports Streamable HTTP. Keep the access token in that client’s private MCP settings.
Write your first request
“The application is already open. If Update is visible, start the update and verify the Ready screen. Then click Start once. If the next window does not appear, enter the Recovery group. Reuse my visual references and tell me what to capture if one is missing.”
This workflow can use a Window check, Find image steps, If/Else branches and bounded retries. Move the readiness check to a reusable group when several flows need it.
What should the assistant do first?
Verify the connection, read the program contract and central guide, then check the timestamp of the device/project snapshot. An old cloud revision must not be presented as the current desktop project.
Describe the actual starting state
“The application is already open, I am on this screen, and I want to find and click this button” avoids unnecessary launch steps. Ask only for missing information that blocks the task: a local path, window, image selection or ambiguous target.
Images stay local
MCP can inspect and edit groups, nested conditions, steps and settings metadata. Downloading or uploading image files over MCP is not part of this design. If a new image is needed, the user crops it locally and supplies its name for the assistant to reference.
Task tracking
The central AI Guide and design-task records help preserve completed work and the pending manual action. When the user says the image is saved, verify that resource and continue from the checkpoint rather than restarting the instructions.
Usage and credits
Capability discovery, module documentation and delivery status checks are free of JAQ credit charges. Project reads and edits use JAQ credits under the account’s rules. Your AI client's usage limits and fees apply separately.
Example requests
- “List the groups and steps in my open project, including the current snapshot timestamp.”
- “Continue if the Ready button is found; otherwise enter Recovery.”
- “Move repeated checks into helper groups and preserve my existing image resources.”
- “Tell me only the missing local selections, then validate the workflow.”
Save, delivery and execution
Validated, saved to the cloud, queued for a device, loaded into the local project and executed are separate states. Queued does not mean loaded or running. Actual execution is started locally.
Codex, Antigravity, Kiro, Claude Code and other clients
Use clients that support the server’s MCP transport and authentication requirements. Follow the current MCP settings for tools such as Codex, Antigravity, Kiro, Claude Code or Cursor. Their versions and configuration steps differ; these names do not imply a formal partnership.
A professional design prompt
“Verify my open project and snapshot time first. Preserve existing resource and step IDs. Propose Preparation, Main task, Common check and Recovery groups. Share repeated work with Call group. Design both branches, explain only necessary local selections and report validation, delivery and local execution separately.”
Connection is not intelligence by itself
MCP exposes tools and a contract to the client. Good results still depend on current state, correct module knowledge, a clear goal, task tracking and real testing.