Build Laravel apps through conversation. Code stored as structured JSON for surgical AI edits.
Most developer tooling work still happens through a UI a human drives. Stellify MCP server moves it into the conversation instead. Build Laravel apps through conversation. Code stored as structured JSON for surgical AI edits.
Model Context Protocol (MCP) server for Stellify - the AI-native code generation platform.
This MCP server lets AI assistants (like Claude Desktop) interact with your Stellify projects to build Laravel and Vue.js applications incrementally. Instead of generating full code files at once, AI can:
The server publishes 14 tools. What each one is for:
Prerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverConfiguration — 1. Get your Stellify API token: - Log into Stellify - Navigate to Settings → API Tokens - Click "Create New Token" -get_project — Get the active Stellify project for the authenticated user. Call this first before any other operations.get_directory — The get_directory tool exposed by this servercreate_directory — The create_directory tool exposed by this servercreate_file — Create a new file in a Stellify project. This creates an empty file shell - no methods, statements, or template yetget_file — Get a file by UUID with all its metadata, methods, and statementssave_file — Save/update a file with its full configuration. This finalizes the file after create_filesearch_files — The search_files tool exposed by this servercreate_method — Create a method signature in a file (without implementation)add_method_body — Parse and add code to a method body. Stellify parses the code into structured JSON statementsInstallation goes through your MCP client rather than a global install: point it at @stellisoft/stellify-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: STELLIFY_API_URL, STELLIFY_API_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Stellify's toolset — Prerequisites, Installation, Configuration and 11 more — is a fair guide to whether it matches your workflow. It is maintained by MattStellisoft; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Stellify's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
| Configuration | 1. **Get your Stellify API token:** - Log into [Stellify](https://stellisoft.com) - Navigate to Settings → API Tokens - Click "Create New Token" - Copy your token |
| get_project | Get the active Stellify project for the authenticated user. **Call this first before any other operations.** |
| get_directory | The get_directory tool exposed by this server. |
| create_directory | The create_directory tool exposed by this server. |
| create_file | Create a new file in a Stellify project. This creates an empty file shell - no methods, statements, or template yet. |
| get_file | Get a file by UUID with all its metadata, methods, and statements. |
| save_file | Save/update a file with its full configuration. This finalizes the file after create_file. |
| search_files | The search_files tool exposed by this server. |
| create_method | Create a method signature in a file (without implementation). |
| add_method_body | Parse and add code to a method body. Stellify parses the code into structured JSON statements. |
| search_methods | Search for methods in the project by name or within a specific file. |
| create_statement | Create an empty statement in a file. This is step 1 of 2 - you must call add_statement_code next. |
{
"mcpServers": {
"stellify": {
"command": "npx",
"args": ["-y", "@stellisoft/stellify-mcp"],
"env": {
"STELLIFY_API_URL": "your-value",
"STELLIFY_API_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| STELLIFY_API_URL | Endpoint or connection string the server talks to. | Yes |
| STELLIFY_API_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.