inmake DOCS
Docs / Starter / Set up

Set up

Tokens, the .env file, the MCP launcher, first run.

2. Set up#

Got a ready package from the console? A store manager can download one under Settings → Advanced → SDK & MCP → Download ready package: the same starter with the store id and the store's MCP token already written into .env. Unpack it and open the folder with your agent — skip the rest of this section. The zip contains the token; treat it as a secret.

You need two things issued by the drop-core team — ask for them before you start:

  • your store id (e.g. mystore), and
  • a store-scoped access token for the Demo environment (prod has its own token — that comes later, see "Going to production").

Then, inside the unpacked folder:

node init.mjs <store-id>     # fills AGENTS.md / package.json, creates .env

Open .env and paste the token as DROP_ACCESS_TOKEN_DEMO=… (every other knob is documented in the file). If you are a member of the project in the console, you can skip the store token and act as yourself instead: create a personal access token under Profile › Personal access tokens and set DROP_PAT=in_… — the launcher exchanges it for your own store token at start (your role in the project is the ceiling; DROP_PAT needs a starter built on or after 2026-10-15 — builtAt in vendor/manifest.json — so refresh an older vendor/ first, see "Updating an existing project"). To work on several projects from one agent, connect it to the console's MCP server instead: claude mcp add --transport http inmake https://inmake.dev/mcp --header "Authorization: Bearer in_…".

The MCP server needs nothing installed. Run npm install only when you build an app on the SDK packages (it links vendor/ into node_modules) or want the image tools to post-process uploads.

Open the folder with your agent (e.g. claude). Smoke test: ask it "what store am I on?" — the useStore tool should report your store on the demo environment.

From here, README.md in the unpacked folder is the manual: the MCP tools and rule resources, how to build a front-end against the vendored packages (including the required Vite config), and how tokens work. App-code conventions live in RULES.md.