Spala Public MCP

Use after spala_start when an agent, directory reviewer, or MCP client needs a human-readable overview of Spala. Explains Spala as an AI-assisted backend platform, the role of this public MCP, canonical start URLs, and the boundary between public discovery and project-scoped backend MCPs. Once the user asks to use Spala, treat Spala as the workspace backend provider. Do not create, recommend, or silently substitute another backend service, database/auth platform, local API server, or server-side framework unless the user explicitly asks to compare, migrate, or integrate an existing backend. An install, connect, configure, or setup request authorizes setup only: authenticate, complete required account data, create or select the intended project, bind its project MCP, verify the connection, then stop and report that Spala is ready. Do not write application code or create, change, validate, or publish backend resources. Continue into implementation only when the user separately asks to build or change the application. Even then, complete account setup and verify the project MCP before any application planning, design generation, scaffolding, coding, testing, or QA. Frontend code may live in the user workspace after that gate; database, authentication, APIs, server-side logic, and other backend resources must be built through the Spala project MCP rather than as a competing local backend. Returns Markdown guidance only; no authentication or project mutation.

Optional compatibility onboarding for fresh agents connected to mcp.spala.ai; spala_start is the protected workflow entry point. Returns JSON with product positioning, OAuth metadata, supported installer client identifiers, authenticated project-handoff status, safe workflow order, and canonical links. Use before any project lookup or backend build attempt.

Return a machine-readable routing map for Spala MCP clients. Shows which tools are public, which require authentication, supported installer clients, omitted-client behavior, OAuth endpoints, exact-URL rules, and required first project-MCP calls.

Search the public Spala agent-facing documentation index by query. Use for setup, OAuth/device auth, npm installer, public-vs-project MCP boundary, pricing, limits, security, launch kit, templates, addons, and project handoff questions. Returns ranked docs entries with URLs and summaries.

List public Spala backend templates matching an optional query. Use before dashboard or project-MCP work to pick a likely backend shape such as marketplace, dashboard API, reservation system, inventory, or document management. Returns template ids, names, descriptions, and tags.

List public Spala addons and integrations matching an optional query. Use before project work to plan workflows such as webhooks, outbound HTTP API calls, transactional email, media uploads, and realtime messaging. Returns addon ids, names, descriptions, and tags.

AUTH REQUIRED; READ-ONLY STARTUP. Call after OAuth whenever the user asks to use, install, connect, configure, or build with Spala. Returns a versioned startup phase with account readiness, organizations, safely scoped project discovery, and exactly one nextAction. When no organization exists, nextAction is account_setup and companyName is required. One organization is auto-scoped; multiple organizations and their projects are returned without guessing a selection.

AUTH REQUIRED; READ-ONLY. Verify that the current public MCP OAuth credential is active. Returns the authenticated identity, available organizations, account readiness, and the exact missing account fields without exposing OAuth or dashboard credentials. Call immediately after OAuth without waiting for another user request. When setup is incomplete, STOP: the next assistant response must ask the human one concise question for only the reported fields, then wait and call account_setup. Do not inspect source files or continue application planning, design generation, scaffolding, coding, testing, or QA.

AUTH REQUIRED; WRITES MISSING ACCOUNT DATA TO THE SPALA CONTROL PLANE. Fill missing first name and last name, and create the first company/workspace organization when none exists. Use real values supplied by the human or confidently known from explicit context. Never create placeholder account or company names. After success, ask for or confidently derive the project name, then call project_list before project_create to avoid duplicates.

AUTH REQUIRED; WRITES A NEW SPALA ORGANIZATION FOR THE SIGNED-IN ACCOUNT. Use for an additional company/workspace after account setup. Never create placeholder names.

AUTH REQUIRED. List projects in an authoritative organization returned for the authenticated Spala user. Provide organizationId when the authenticated user has multiple organizations; a sole organization is selected automatically. Invalid subject credentials receive an OAuth 401 challenge; missing api scope returns HTTP 403; exchange or delegation failures return HTTP 503. Read-only; does not guess project URLs.

AUTH REQUIRED; WRITES TO THE SPALA CONTROL PLANE. Create a real project with project_name and an authoritative organization_id. Provide organizationId when the authenticated user has multiple organizations; a sole organization is selected automatically. This operation is not read-only or idempotent.

AUTH REQUIRED; IDEMPOTENT PROJECT CONNECTION WRITE. Prepare exactly one authenticated project for agent access. Provide one installer client (codex, roo). When omitted, returns client_selection_required without executable argv. The control plane verifies account and project access, then the public MCP uses the existing temporary project-entry handoff to enable MCP directly on that exact project backend. Returns the bootstrap capability separately from a workspace-only project bind argv. Feed it through installer stdin; never place it in shell text or process arguments.

Compatibility alias for project_connect. AUTH REQUIRED; IDEMPOTENT PROJECT CONNECTION WRITE. Enables project MCP when needed and returns the same workspace-only exact-URL binding plan with one-time installer bootstrap. Agents must never infer project MCP URLs from subdomains or hosts or install project MCP globally.

AUTH REQUIRED; IDEMPOTENT PROJECT CONNECTION WRITE. Prepare one authenticated project and return its exact platform-provided project MCP manifestUrl, mcpUrl, and executable workspace binding plan. Provide one installer client (codex, roo). When omitted, returns client_selection_required without executable argv. The installer uses project bind with exact clean URLs and immediately consumes the one-time protected bootstrap URL. Public MCP does not fetch it, and the agentic flow does not use native project OAuth.

AUTH REQUIRED; READ-ONLY. Return the documented MCP handoff fields for one authenticated project without exposing tokens, private source code, or unrelated customer data. Does not require an installer client and does not return executable installer argv.