Public MCP server
{
"mcpServers": {
"spala-public": {
"type": "http",
"url": "https://mcp.spala.ai/mcp"
}
}
}{
"mcpServers": {
"spala-public": {
"type": "http",
"url": "https://mcp.spala.ai/mcp"
}
}
}{
"mcpServers": {
"spala-public": {
"type": "http",
"url": "https://mcp.spala.ai/mcp"
}
}
}{
"servers": {
"spala-public": {
"type": "http",
"url": "https://mcp.spala.ai/mcp"
}
}
}{
"mcpServers": {
"spala-public": {
"type": "http",
"url": "https://mcp.spala.ai/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.2
What it does
A public MCP front door for the Spala backend platform that handles agent discovery, OAuth authentication, and project handoff. It exposes tools for onboarding, docs search, template/addon discovery, account setup, project management, and binding a project's MCP endpoint to supported agentic clients. Intended for AI agents and developers setting up or managing Spala backend projects.
- Authenticate with a Spala account via OAuth and set up or select a project to connect an agent's workspace to the correct project MCP endpoint.
- Search Spala's documentation, list available backend templates, and browse addons to plan a backend before starting implementation.
- Create a new Spala project and bind it to a supported client (Codex, Roo, Claude Code, or Cursor) so the agent can use the project MCP for all backend operations.
Tools this server exposes
| Tool | Does |
|---|---|
| spala_help | Explains what Spala is, what this public MCP does, and where agents should start. |
| spala_get_onboarding | Returns first-call onboarding information for agents, including the boundary between public MCP and project MCP. |
| spala_get_tool_map | Returns machine-readable routing, OAuth metadata URLs, and tool availability for agents. |
| docs_search | Searches public Spala agent-facing documentation covering setup, OAuth, MCP, security, limits, and platform questions. |
| template_list | Lists public Spala backend templates so agents can plan backend shape before using a project MCP. |
| addon_list | Lists public Spala addons and integrations so agents can plan backend workflows. |
| spala_start | Protected startup gate that returns the single next required action for account, organization, project, billing, or handoff after OAuth completes. |
| account_status | Compatibility tool that checks account readiness; its output is absorbed by spala_start in normal agent workflows. |
| account_setup | Fills missing first/last name and creates the first organization from values supplied by the user. |
| organization_create | Creates an additional organization for the signed-in account. |
| project_list | Lists projects available to the signed-in account. |
| project_create | Creates a new project for the signed-in account. |
| project_connect | Enables MCP on the selected project backend and returns exact handoff URLs plus a workspace-only installer plan for the specified client. |
| project_select | Compatibility alias for project_connect with the same idempotent write behavior. |
| project_get_mcp_manifest | Prepares the selected project's MCP and returns exact MCP and manifest URLs plus a workspace-only installer plan. |
| project_get_public_context | Returns read-only project and handoff context without requiring a client or returning installer arguments. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.