aicoded.dev

MCP: the tools for your AI assistant

aicoded mcp gives your AI assistant the tools of aicoded over MCP: it creates apps, checks them, previews them in aicoded dev, reads what went wrong, publishes them, runs their previews on the platform, releases a publish held for preview, reads their logs and traces there, and reads these docs offline. No tool runs a shell command or takes a file path, and nothing a tool returns of aicoded dev holds a secret value.

Setting it up

aicoded mcp [dir] serves MCP on standard input and output for the workspace dir, the current folder by default. For Claude Code, run this in the workspace folder:

claude mcp add aicoded -- aicoded mcp

The MCP setup page of the dev UI shows the commands for Claude Code and Codex, and the .cursor/mcp.json for Cursor, with the full paths of this aicoded and of the workspace.

The tools

Tool What it does
app_create creates a new app in its own folder of the workspace, as aicoded init does, with its AGENTS.md
check runs lint's precheck of GOFLAGS and the vendor folder, aicoded generate, the check of the draft .aicoded/migration.sql, go build, go vet, the lint rules for app code and the tests for every app or one, and lists each problem with its code, file:line and fix, and each app's notes in the same shape, which do not fail the check; frozen writes nothing
preview builds and starts, or restarts, an app in aicoded dev, and returns its state and local address, or the problems that stop it
what_broke lists what went wrong: the problems of failed apps, the last error log lines and the last failed spans
describe summarises the apps, as aicoded describe --json does, with each app's local setup in dev.yaml: the workspace, whether mysql is set, the personas with their roles and groups, and each of its settings and secrets with whether it is set, never a value
howto shows a page of the docs, or lists them all with their summaries
logs the newest log lines of the apps, by app, lowest level, trace or text; with env preview or production, those of one app on the platform, as aicoded logs reads them
traces the newest traces, each request or call across the apps, by app or with an error only; with env, those of one app on the platform, from its newest 1000 spans
trace every span of one trace, in start order; with env and app, that app's spans of the trace on the platform
mail_list the mail an app sent, which aicoded dev caught, and its mailbox, newest first
mail_get one message from mail_list
mail_receive delivers a test message to an app's inbox, as if it had arrived by mail
publish does what aicoded publish --no-wait does for an app, with a summary of the change and, with release: true, as --release does, and returns the publish's id, app and commit, whether it created the app, whether it skips the preview (release), and what to do next
release_status shows a publish by its id, as aicoded status --json does: its status, steps, problems and notes, and the decision on releasing it, with the address of a live release in release.url; for a publish held for preview, next says to start its preview with preview_publish unless it runs, to give you its address, and to call release only when you ask, and, for one that replaced an older publish waiting for approval or going live, to tell you so
release asks for the release of a publish held for preview, as aicoded release --no-wait does, and returns the publish, as release_status does, and what to do next
preview_publish runs a publish that passed as its app's preview on the platform, as aicoded preview <id> does, for a held publish when release_status's next says so and otherwise only when you ask, and returns its app, host, url, publish, started, expires, whether its data was reset, and what to do next
preview_end ends the preview of an app on the platform, as aicoded preview end does, which deletes its data

All but app_create, check, preview, mail_receive, publish, release, preview_publish and preview_end only read; preview_publish and preview_end may delete a preview's data, and release may replace what production runs, so your AI assistant may ask you before it calls them. publish, release_status, release, preview_publish, preview_end, and logs, traces and trace with env set to preview or production, reach the platform, with your sign-in; the other tools stay on this computer. On the platform, logs, traces and trace also take since and until, as aicoded logs does, read one app, which you must own, and refuse contains; their answers have the shape of those of aicoded dev. Production logs hold what the app logged while people used it, which can be personal data: the server tells the assistant to read them only when you ask. Tools name apps by the app: line of their aicoded.yaml, never by a folder or a path (E-DEV-014).

The docs

howto serves the same pages as aicoded explain:

They are also the MCP resources aicoded://docs/<path> for the guides and the task recipes, such as aicoded://docs/guides/forms and aicoded://docs/tasks/add-form, aicoded://errors/<CODE> for the error pages, and aicoded://changelog for the changelog for AI assistants. An unknown topic is E-CLI-001.

The loop

The server tells the assistant to start with howto guides/overview, and to work in this loop:

  1. app_create makes a new app. Then it edits the app's files.
  2. check generates the code, builds the apps and runs go vet, the lint rules for app code and the tests. It fixes every problem listed.
  3. preview builds and starts an app in aicoded dev and returns its local address.
  4. When something fails, what_broke lists the failed apps, error log lines and failed spans.
  5. Only when you ask it to publish an app, it commits everything, calls publish with the app and a summary of the change, then calls release_status with the id until the publish ends, tells you the outcome, with whether it goes live and, once it is live, its address from release.url, and fixes its problems as it fixes those of check. When it is not signed in (E-CLI-004), it asks you to run aicoded login: there is no tool for signing in. A publish is held for your preview: once it passed, it starts the preview with preview_publish, as release_status says, and gives you the address. It calls release only when you ask to release it, and passes release: true to publish only when you ask to publish straight to production. A new publish replaces one waiting for approval, whose card goes.
  6. Apart from the preview of a held publish, it calls preview_publish only when you ask, with a publish that passed, and gives you the preview's address, and preview_end when you ask to end it. It invites no one: you pick who sees the preview, in the console.

The server also tells it never to open, print or copy dev.yaml, credentials.json or any other file of aicoded's config folder, as they hold passwords and keys: describe tells which local values and personas are set, and aicoded whoami the organisation and the sign-in.

It writes app, owner, data, email, settings and secrets in the permission list by hand, and never edits what aicoded generate writes: the access and services sections, every *_gen.go and *_gen.ts file, pages/assets_gen/ and .aicoded/.

Which aicoded dev it uses

See also

Markdown · Source on GitHub · framework f46741f