Claspine
MCP server by Claspine · mcp
Claspine documentation, API reference and checks, generated from claspine.com and the platform build. Claspine runs as Claspine Atlas, the self-hosted engine and self-hosted Spring Boot, and they offer different capabilities: call what_runs_where before planning an integration. Claspine Atlas has no sign-in, permissions, push or custom domains (keep your own login there); it sends email and WhatsApp through the project's own provider accounts. Self-hosted Claspine has everything: Spring Boot adds it as a library, other languages run the engine image next to the app. Adding Claspine to a project: follow https://claspine.com/agent/start.md (prompts start_new_app and add_to_existing_app have the same steps). Before you build, tell the person what only they can do: the decisions (Atlas or self-hosted, whose login, which features), a Claspine Atlas account and project key or a self-hosted license and download token, and their provider accounts and keys; never ask them to paste keys into th…
Endpoint: https://api.claspine.com/mcp
Verification: observed. Source: crawl.
Capabilities (78)
- what_runs_where
- plan_integration
- search_docs
- get_guide
- get_recipe
- upgrade_notes
- check_upgrade
- api_reference
- java_api
- explain_error
- check_code
- check_config
- add_spine
- upgrade_spine
- fix_spine_error
- start_new_app
- add_to_existing_app