Documentation

Getting Started

Sign up and start building with Stellify

Visit stellisoft.com/register to register. A new account comes with a project ready to build in — the fastest way to see what Stellify is for is to run one pass of the development loop.

Your First Loop

1. Connect your editor. Grab an API token from User SettingsAPI Tokens, then add the MCP server to Claude Code, Cursor, or VS Code:

{
  "mcpServers": {
    "stellify": {
      "command": "npx",
      "args": ["@stellify/mcp"],
      "env": {
        "STELLIFY_API_URL": "https://api.stellisoft.com/api/v1",
        "STELLIFY_API_TOKEN": "your-api-token-here"
      }
    }
  }
}

2. Ask for a feature. In your editor's chat:

Add user registration to my Stellify project — check the library for an existing flow first

Watch what the agent does: it searches Stellify's shared library, finds a proven registration flow, references it into your project — routes, controller, validation, the lot — and wires it to your models. What doesn't exist yet it scaffolds. Then it runs the code and the tests to prove the feature works. That's the difference from a code generator: the agent's first move is to find working code, not to write plausible code.

3. Sync it back. Connect a repository in Project Settings → GitHub Integration and commit the assembled feature to your repo — or export the whole project as a standard Laravel app. Your repo stays the source of truth.

Feature shipped. Run the loop again for the next one. The full tool reference is on The MCP Server page.

The Other Ways In

The cloud editor. Everything the agent touches is also editable in the browser — the Code Editor for method-level PHP and JavaScript, the Interface Builder for visual UI work, and a built-in AI chat with the same tools. Most people let the agent do the heavy lifting and use the editor to refine. Take the tour to get oriented.

Bring existing code. Point the loop at what you already have: import a codebase via MCP (any framework — the agent converts it), connect a GitHub repo in project settings, or parse a local Laravel project with the Stellify Laravel package.

Before You Build in Earnest

  1. Connect a database — bring your own MySQL/PostgreSQL or use the Supabase wizard; migrations run against it from the editor or via the agent
  2. Enable capabilities — auth, payments, mail: whatever your app depends on, switched on in Project Settings
  3. Invite your teamcollaborators with granular permissions, when you're ready