Stellify MCP

Stellify MCP Server

Model Context Protocol (MCP) server for Stellify - the AI-native code generation platform.

What is This?

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:

• Create file structures (classes, controllers, models, middleware, Vue components)
• Add method signatures with type hints
• Parse PHP/JavaScript code into structured JSON (statement-by-statement)
• Convert HTML to Stellify elements in a single operation
• Search existing code in your projects
• Install reusable code from the global library
• Build applications through natural conversation

Quick Start — Hosted Server (recommended)

The easiest way to connect is the hosted server at https://api.stellisoft.com/mcp. No install, no Node.js, no API token — your MCP client opens a browser window where you sign in with your Stellify account and approve access (OAuth).

Claude (web or desktop): Stellify is listed in the Claude connectors directory — go to Settings → Connectors, find Stellify, and click Connect. Or choose Add custom connector and paste https://api.stellisoft.com/mcp.

Claude Code:

claude mcp add --transport http stellify https://api.stellisoft.com/mcp

Cursor (.cursor/mcp.json):

{

"mcpServers": { "stellify": { "url": "https://api.stellisoft.com/mcp" } } }

VS Code (.vscode/mcp.json):

{

"servers": { "stellify": { "type": "http", "url": "https://api.stellisoft.com/mcp" } } }

Windsurf (~/.codeium/windsurf/mcp_config.json):

{

"mcpServers": { "stellify": { "serverUrl": "https://api.stellisoft.com/mcp" } } }

Local Install (npm alternative)

Prefer to run the server locally? The npm package speaks the same protocol against the same platform API, authenticated with an API token instead of OAuth.

Prerequisites

• Node.js 18 or higher
• A Stellify account - Sign up at stellisoft.com
• Claude Desktop (or another MCP-compatible AI client)

Installation

Install globally via npm:

npm install -g @stellisoft/stellify-mcp

Configuration

1. Get your Stellify API token:

• Log into Stellify
• Navigate to Settings → API Tokens
• Click "Create New Token"
• Copy your token

1. Configure Claude Desktop:

Edit your Claude Desktop configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/claude/claude_desktop_config.json

Add the Stellify MCP server:

   {

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

1. Restart Claude Desktop

That's it! The Stellify tools should now be available in Claude Desktop.

Usage

Once configured, you can talk to Claude naturally to build applications:

Example Conversations

Create a new controller:

"Create a UserController in my Stellify project"

Add methods:

"Add a method called 'store' that takes a Request parameter and returns a JsonResponse"

Implement method logic:

"Add this implementation to the store method:

$user = User::create($request->validated()); return response()->json($user, 201);"

Build a Vue component:

"Create a Counter component with an increment button"

Convert HTML to elements:

"Convert this HTML to Stellify elements:

Hello Click me "

Search your codebase:

"Search for all controller files in my project"

"Find methods related to authentication"

Available Tools

Project & Directory Tools

get_project

Get the active Stellify project for the authenticated user. Call this first before any other operations.

Parameters: None

Returns:

• uuid: Project UUID (needed for most operations)
• name: Project name
• directories: Array of {uuid, name} for existing directories

---

get_directory

Get a directory by UUID to see its contents.

Parameters:

• uuid (required): The UUID of the directory

---

create_directory

Create a new directory for organizing files.

Parameters:

• name (required): Directory name (e.g., "js", "css", "components")

---

File Tools

create_file

Create a new file in a Stellify project. This creates an empty file shell - no methods, statements, or template yet.

Parameters:

• directory (required): UUID of the directory (get from get_project directories array)
• name (required): File name without extension (e.g., "Counter", "UserController")
• type (required): File type - "class", "model", "controller", "middleware", or "js"
• extension (optional): File extension. Use "vue" for Vue components.
• namespace (optional): PHP namespace (e.g., "App\\Services\\"). Only for PHP files.
• includes (optional): Array of fully-qualified class names to import (e.g., ["App\\Models\\User", "Illuminate\\Http\\Request"]). Stellify will resolve these to file UUIDs, fetching from Laravel API or vendor directory if needed.

Directory selection: Match the directory to your file's purpose. If the directory doesn't exist, create it first with create_directory.

Example workflow:

1. create_file → creates empty shell, returns file UUID
2. create_statement + add_statement_code → add variables/imports
3. create_method + add_method_body → add functions
4. html_to_elements → create template elements (for Vue)
5. save_file → finalize with all UUIDs wired together

Auto-dependency creation (when auto_create_dependencies: true):

When you create a file with code like:

<?php

namespace App\Http\Controllers;

use App\Models\User; use Illuminate\Http\Request;

class UserController extends Controller { public function store(Request $request) { $user = User::create($request->validated()); return response()->json($user); } }

Stellify will:

1. Parse use statements to find dependencies (User, Request, Socialite)
2. Check Application DB for framework classes → find cached classes
3. For core Laravel classes → fetch from api.laravel.com
4. For vendor packages (Socialite, Spatie, etc.) → read from vendor/ directory
5. Create missing App classes → create User model file
6. Wire up the file's includes array with all dependency UUIDs

Supported sources:

• Laravel API - Core Illuminate\* classes fetched from api.laravel.com
• Vendor packages - Laravel\Socialite\*, Laravel\Cashier\*, Spatie\*, Livewire\*, etc. read directly from your vendor/ directory using PHP-Parser

The response includes a dependencies report showing what was created/resolved and from which source.

---

get_file

Get a file by UUID with all its metadata, methods, and statements.

Parameters:

• uuid (required): UUID of the file

---

save_file

Save/update a file with its full configuration. This finalizes the file after create_file.

Parameters:

• uuid (required): UUID of the file
• name (required): File name (without extension)
• type (required): File type ("js", "class", "controller", "model", "middleware")
• extension (optional): File extension ("vue" for Vue SFCs)
• template (optional): Array of root element UUIDs for Vue section
• data (optional): Array of METHOD UUIDs only (functions)
• statements (optional): Array of STATEMENT UUIDs (imports, variables, refs)
• includes (optional): Array of file UUIDs to import

Important: data = method UUIDs only, statements = statement UUIDs (code outside methods)

---

search_files

Search for files in the project by name or type.

Parameters:

• name (optional): File name pattern to search for
• type (optional): File type filter

---

Method Tools

create_method

Create a method signature in a file (without implementation).

Parameters:

• file (required): UUID of the file to add the method to
• name (required): Method name (e.g., "increment", "store", "handleClick")
• visibility (optional): "public", "protected", or "private" (PHP only, default: "public")
• is_static (optional): Whether the method is static (PHP only, default: false)
• returnType (optional): Return type (e.g., "int", "string", "void")
• parameters (optional): Array of {name, type} objects

---

add_method_body

Parse and add code to a method body. Stellify parses the code into structured JSON statements.

Parameters:

• file_uuid (required): UUID of the file containing the method
• method_uuid (required): UUID of the method to add code to
• code (required): Code for the method body (just the statements, no function declaration)

Example:

code: "return $a + $b;"

---

search_methods

Search for methods in the project by name or within a specific file.

Parameters:

• name (optional): Method name to search for (supports wildcards)
• file_uuid (optional): Filter results to a specific file

---

Statement Tools

create_statement

Create an empty statement in a file. This is step 1 of 2 - you must call add_statement_code next.

Parameters:

• file (optional): UUID of the file to add the statement to
• method (optional): UUID of the method to add the statement to (for method body statements)

Use cases:

• PHP: Class properties, use statements, constants
• JS/Vue: Variable declarations, imports, reactive refs

---

add_statement_code

Add code to an existing statement. This is step 2 of 2 - call after create_statement.

Parameters:

• file_uuid (required): UUID of the file containing the statement
• statement_uuid (required): UUID of the statement to add code to
• code (required): The code to add

Examples:

code: "use Illuminate\\Http\\Request;"

code: "const count = ref(0);" code: "import { ref } from 'vue';"

---

get_statement

Get a statement by UUID with its clauses (code tokens).

Parameters:

• uuid (required): The UUID of the statement

---

Route Tools

create_route

Create a new route/page in a Stellify project.

Parameters:

• project_id (required): The UUID of the Stellify project
• name (required): Route/page name (e.g., "Home", "Counter", "About")
• path (required): URL path (e.g., "/", "/counter", "/about")
• method (required): HTTP method ("GET", "POST", "PUT", "DELETE", "PATCH")
• type (optional): Route type - "web" for pages, "api" for API endpoints (default: "web")
• data (optional): Additional route data

---

get_route

Get a route/page by UUID.

Parameters:

• uuid (required): The UUID of the route

---

search_routes

Search for routes/pages in the project by name.

Parameters:

• search (optional): Search term to match route names
• type (optional): Filter by route type ("web" or "ap