Spala Public MCP

Name: Spala Public MCP
Author: Spala AI

@Spala AI

Repository Homepage Documentation

About Spala Public MCP

Connect agents to Spala discovery, OAuth metadata, and project MCP handoff guidance.

#spala #mcp #agents #ai backend #backend builder #oauth #no-code backend #api #templates #developer tools

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "spala_public_mcp": {
      "type": "http",
      "url": "https://mcp.spala.ai/mcp"
    }
  }
}

Tools

Explains what Spala is, how the public MCP is used, and where agents should go next.

Returns public onboarding guidance for agents and developers evaluating Spala.

Shows the boundary between this public MCP and authenticated project MCP servers.

Searches public Spala docs for onboarding, auth, MCP, templates, addons, and workflow guidance.

Lists public backend templates that can help agents understand common Spala project patterns.

Lists public Spala addons and capabilities.

Reports whether the current MCP request has authenticated Spala platform context.

Lists available Spala projects after authentication so agents can choose a project safely.

Creates or dry-runs a new Spala project when supported by the authenticated platform context.

Selects an authenticated project and returns the correct project MCP handoff details.

Explains how to connect to the selected project MCP for build, validate, publish, and review workflows.

Overview

What is Spala Public MCP?

Spala Public MCP is the public Model Context Protocol front door for Spala, an AI-assisted backend platform for creating project backends, APIs, auth, database models, functions, tasks, and publishable API contracts.

Use this remote MCP server for discovery: it explains what Spala is, returns onboarding/tool-map data for agents, exposes public docs/templates/addons, and advertises the canonical Spala OAuth metadata. Backend changes are intentionally handled by the selected project MCP after Spala platform authentication.

Remote server

MCP endpoint: https://mcp.spala.ai/mcp
Transport: Streamable HTTP
Install manifest: https://mcp.spala.ai/mcp/install-manifest
OAuth protected resource: https://mcp.spala.ai/.well-known/oauth-protected-resource
OAuth authorization server: https://mcp.spala.ai/.well-known/oauth-authorization-server

What agents can do

Learn Spala's public onboarding flow before signing in.
Search agent-facing Spala docs.
List backend templates and addons.
Discover the boundary between public MCP and project MCP.
Receive OAuth guidance for Spala platform authentication.
Avoid hardcoding project MCP URLs; project handoff must use explicit URLs returned by Spala.

Tools

spala_help
spala_get_onboarding
spala_get_tool_map
docs_search
template_list
addon_list
auth_status
project_list
project_create
project_select
handoff_to_project_mcp

Boundary

The public MCP does not directly mutate customer project backends. Project operations fail closed in this standalone release until a verified platform/project handoff contract is available. After an authenticated project MCP is selected, agents should use that project MCP for build, validate, publish, and review workflows.

Client setup

codex mcp add spala_public_mcp --url "https://mcp.spala.ai/mcp"
codex mcp login spala_public_mcp --scopes api
gemini mcp add --scope user --transport http spala_public_mcp "https://mcp.spala.ai/mcp"