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

Basic information

Runtime

node

Publisher

Spala AI

Submitted by

Paul Bogosta

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

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

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.

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"