# Spala Public MCP [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/spala-ai/spala-public-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 1022  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/spala-public-mcp-2

## Description
Discovery, OAuth, project operations, and exact project MCP handoff for Spala backend projects.

## Tools
Capabilities this server exposes over MCP:

- **spala_start**
- **project_connect**

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "spala-public-mcp": {
    "command": "npx",
    "args": ["--yes","@spala-ai/mcp-install"],
    "env": {
      "PUBLIC_BASE_URL": "",
      "SPALA_API_BASE_URL": "",
      "PUBLIC_OAUTH_ENCRYPTION_SECRET": "",
      "PUBLIC_MCP_PLATFORM_SERVICE_SECRET": ""
    }
  }
}
```

**Requires environment variables:** `PUBLIC_BASE_URL`, `SPALA_API_BASE_URL`, `PUBLIC_OAUTH_ENCRYPTION_SECRET`, `PUBLIC_MCP_PLATFORM_SERVICE_SECRET` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Spala Public MCP MCP server does

Spala Public MCP MCP server acts as the public control-plane entry point for Spala. It explains the service, exposes onboarding and routing metadata, searches agent-facing documentation, and lists backend templates and addons. After a user explicitly authorizes access from the current MCP client, it can inspect account readiness, create or select an organization, list or create projects, and prepare the handoff to a project-specific MCP.

The service keeps account and project setup separate from application implementation. A setup request should end after authentication, project selection or creation, MCP binding, and connection verification. Database, authentication, API, and server-side changes are expected to happen through the selected project MCP rather than this public endpoint.

## How it works

The hosted MCP endpoint is `https://mcp.spala.ai/mcp`. OAuth discovery is published from the same public origin, while authorization sends the user to the Spala dashboard for sign-in or account creation. The public MCP uses a bearer with the `api` scope for protected operations and delegates project requests server-side. Credentials are not returned in tool results or error messages.

The normal workflow begins with `spala_start`, but only after the user has explicitly asked the current client to access their Spala account or project and OAuth has completed. That gate returns the next required account, organization, project, billing, or handoff action. `project_connect` then enables MCP for the chosen project backend and returns exact handoff URLs plus a workspace-only installer plan. `project_select` is a compatibility alias with the same write behavior.

## Setup and configuration

For local development, install dependencies with `pnpm install` and run `pnpm dev`; the default URL is `http://localhost:4100/mcp`. A production-style local run uses `pnpm build` followed by `pnpm start`. Copy `.env.example` to `.env` before running locally.

Required configuration includes the public service origin, validated Spala API origin, a dedicated OAuth encryption secret, and the internal platform service secret. HTTPS deployments also require a persistent OAuth replay-state directory shared by service workers. Other settings control OAuth lifetimes and limits, MCP request limits, platform timeouts, response sizes, browser CORS origins, dashboard and pricing URLs, and optional trusted runtime origins.

Clients configure only the public MCP URL. The repository also publishes an install manifest, OAuth metadata, a public profile, a smoke test, an npm installer, and Postman resources for discovery and testing.

## Tools and capabilities

Spala Public MCP MCP server exposes public discovery tools such as `spala_help`, `spala_get_onboarding`, `spala_get_tool_map`, `docs_search`, `template_list`, and `addon_list`. Protected tools cover account status and setup, organization creation, project listing and creation, project connection, MCP manifest generation, and read-only project context.

The service returns exact project MCP and manifest URLs supplied by the control plane. `project_get_mcp_manifest` prepares the selected project’s MCP and returns an installer plan, while `project_get_public_context` provides handoff context without installer arguments. These operations support agent setup and routing, not direct mutation of project backend resources.

## Limitations and notes

Product questions, comparisons, research, and tests through another client must not initiate OAuth. The public MCP should not scaffold an alternative backend, inspect application files, generate designs, write code, test, or perform QA during setup. It also should not directly modify project backend resources. Continue into implementation only after a separate build or change request and successful project MCP verification.

The optional contract smoke test uses `SPALA_MCP_INSTALLER_ROOT` to point at a local installer checkout. It verifies generated binding arguments, scoped project mounts, one-time bootstrap POST handling, and Claude Code binding behavior.

_Full upstream README: https://allmcps.com/mcp/spala-public-mcp-2/readme_