Reference

The SDK packages, the mapled CLI, the MCP tools and the delivery HTTP API.

  • SDK packages — the packages a site reads Mapled through, and which one fits your stack.
  • CLI — every mapled command: sign-in, types, the schema pin, the manifest, MAPLED.md, forms, doctor, preview.
  • MCP tools — every tool an AI agent calls, with its parameters.
  • HTTP API — the delivery API under every SDK: reads, the release pointer, forms, live data, the publish webhook.

Each package's README on npm is its full reference: @mapled/next, @mapled/astro, @mapled/nuxt, @mapled/client, @mapled/react, @mapled/vanilla, @mapled/cli, @mapled/mcp.

For AI agents, Mapled serves its own guide at https://api.mapled.io/agents.md and a summary at https://api.mapled.io/llms.txt.

  • SDK packages · The packages a site reads Mapled through — what each one adds and the first read in each.
  • CLI · Every mapled command — sign-in, every agent tool from the shell, types, the schema pin, the manifest, MAPLED.md, forms, doctor, preview and the server key on the host.
  • MCP tools · Every tool Mapled's MCP server offers an AI agent, with its input — the same tools mapled tool calls from the shell.
  • HTTP API · The delivery API under every SDK — reads, the release pointer, forms, live data, site users and the publish webhook.