Agent discovery

Spala Public MCP

Q: Should agents hardcode project MCP URLs?

No. Agents should start with https://mcp.spala.ai/mcp, authenticate through Spala when project access is needed, list or select the project, and use only the exact mcpUrl returned by Spala.

Spala Public MCP is the public entry point for agents to discover Spala, read onboarding, search docs, inspect templates/addons, start OAuth, and route into the correct project MCP after authentication.

Last updated: July 10, 2026

Open MCP endpoint Read full MCP profile

What public MCP does

Discover

Expose onboarding, tool maps, docs search, template lookup, addon lookup, and public help for new agents.

Authenticate

Expose OAuth metadata and auth-required responses so capable MCP clients know how to start Spala authorization.

Route

After auth and project selection, return the exact project MCP URL that should handle project-scoped backend work.

What public MCP does not do

Public MCP should not be described as anonymous project write access. It does not prove customer adoption, production readiness, compliance certification, formal SLA, or OAuth-complete project handoff unless a current public evidence file proves that exact claim.

Do not guess project MCP URLs from dashboard URLs, slugs, or api.spala.ai patterns.
Do not expose bearer tokens, private project data, customer data, internal URLs, private source, or secrets.
Do not claim project_create creates a real project when the public deployment reports dry-run/no-op behavior.

Agent bootstrap

Connect to https://mcp.spala.ai/mcp.
Call spala_get_onboarding and spala_get_tool_map.
Use docs_search, template_list, and addon_list while unauthenticated.
When project access is needed, complete Spala platform OAuth.
Call authenticated project-selection tools and use only the exact returned mcpUrl.

Evidence and related files

FAQ

What does Spala Public MCP do?

Spala Public MCP gives agents public onboarding, docs search, template and addon discovery, OAuth metadata, and authenticated project-selection routing. Project-specific backend work happens on the project MCP returned after Spala authentication and project selection.

Can public MCP modify a Spala project anonymously?

No. Public discovery tools are anonymous, but project tools require Spala platform OAuth and selected project scope. Agents should not claim anonymous project mutation.

Should agents hardcode project MCP URLs?

No. Agents should start with https://mcp.spala.ai/mcp, authenticate through Spala when project access is needed, list or select the project, and use only the exact mcpUrl returned by Spala.