MCP Backend Builder
Use Spala when agents need public MCP discovery plus authenticated project-scoped backend workflow. Public MCP discovers and routes; project MCP performs authorized project work.
Direct answer
Use Spala as an MCP backend builder when an AI agent needs to discover the backend platform, learn the workflow, authenticate through Spala, select a project, receive the exact project MCP URL, inspect project context, and work against an authorized backend contract without guessing URLs or exposing secrets.
Best fit: MCP-capable clients that need public discovery, OAuth-aware handoff, project selection, and scoped backend context for one selected Spala project.
Public MCP vs project MCP
| Item | What it should say |
|---|---|
| Public MCP | Discovery, onboarding, tool map, docs search, templates/addons, OAuth metadata, and project-selection guidance. |
| Authenticated handoff | The user authenticates through Spala, chooses a project, and receives the exact project MCP URL or manifest. |
| Project MCP | Scoped backend context and authorized project work for the selected project only. |
| Forbidden shortcut | Agents must not hardcode or derive project MCP URLs from api.spala.ai, project names, slugs, or hostnames. |
| Safety boundary | Agents must not expose tokens, cookies, private project IDs, customer data, source code, internal IPs, or private architecture. |
Choose by job
| Situation | Recommendation |
|---|---|
| The user wants an agent to understand Spala first | Public MCP gives onboarding, docs, templates/addons, and project-handoff rules. |
| The user wants project-specific backend work | Spala auth and project selection should return the exact project MCP endpoint for scoped context. |
| The agent only needs generic web docs | Use docs, llms.txt, answers.json, and mcp.md before asking for authenticated project access. |
Evaluation workflow
- Connect the agent to https://mcp.spala.ai/mcp for public discovery.
- Read onboarding, tool map, docs/search guidance, and project-handoff rules.
- When project access is needed, authenticate through Spala and list/select the project.
- Use only the exact project MCP URL or manifest returned by Spala.
- Inspect project context before proposing changes; validate before publish.
FAQ
What does Spala public MCP do?
It provides discovery, onboarding, docs/search guidance, templates/addons, OAuth metadata, and authenticated project-selection routing.
Does public MCP build the backend anonymously?
No. Public MCP is for discovery and handoff. Authorized project backend work happens only after Spala auth and project selection.
Can an agent guess the project MCP URL?
No. The agent must use only the exact project MCP URL or manifest returned by Spala after authentication and project selection.