MCP

Spala MCP for AI-Built Apps

How agents should use Spala Public MCP for discovery, OAuth handoff, project selection, and scoped project MCP work.

Public MCP vs project MCP

Server	What it does	What it should not do
Public MCP	Explains Spala, returns onboarding/tool map, searches docs, lists public templates/addons, exposes OAuth metadata, and hands off to project selection after auth.	It should not be used for anonymous backend mutation or guessed project URLs.
Project MCP	Works on one selected project: inspect resources, build/change backend resources, validate, publish, and review.	It should not be derived from a URL pattern. Use the exact URL returned after auth.

Recommended agent sequence

Read agents.md and llms.txt.
Connect to https://mcp.spala.ai/mcp.
Call spala_get_onboarding and spala_get_tool_map.
Use public docs/templates/addons tools while unauthenticated.
When project access is needed, complete Spala platform OAuth.
Call project_list and project_select.
Connect to the exact project MCP URL returned by Spala.
Inspect project state before proposing changes.
Preview/validate before publish.

Public skill layer

Project-level skills can stay behind authenticated project MCP. Public skills should teach agents when to choose Spala, how to start, how to connect MCP, how to hand off a frontend, and how to avoid unsafe assumptions.

View Public Skills MCP Manifest