build_plan — Supero MCP Tool
build_plan
(build plan) is one of 64 tools on the
Supero
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call build_plan from your client
- Claude Code Supero build_plan run in your project directory
- Claude Desktop Supero build_plan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Supero build_plan ~/.cursor/mcp.json
- VS Code Supero build_plan .vscode/mcp.json
- Zed Supero build_plan ~/.config/zed/settings.json
- Windsurf Supero build_plan ~/.codeium/windsurf/mcp_config.json
- Cline Supero build_plan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Supero build_plan ~/.gemini/settings.json
- Grok Supero build_plan .mcp.json (in your project root)
- ChatGPT Supero build_plan Settings → Connectors → Advanced → Developer mode
- Claude.ai Supero build_plan Settings → Connectors → Add custom connector
- LangChain Supero build_plan pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http supero https://api.supero.dev/mcp/v1/messagesOther tools on this server
- crud_search
- crud_get
- crud_create
- crud_update
- crud_delete
- schema_list
- schema_get
- schema_validate
- schema_save
- schema_delete
- schema_list_project
- schema_update
- project_link_schemas
- sdk_generate
- sdk_status
- sdk_list
- sdk_download
- rbac_get_my_access
- rbac_check_permission
- apikey_get_scope
- connector_run
- connector_cancel
- connector_status
- connector_enable
- connector_disable
- connector_discover
- connector_discover_status
- connector_discover_results
- connector_test_config
- connector_test
- connector_plugins
- build_get_skills
- build_get_examples
- build_get_service_contract
- build_whoami
- build_list_projects
- build_get_project
- build_create_project
- build_update_project
- build_set_project_mode
- build_replace_project
- build_validate
- build_publish
- build_stage_bundle
- build_get_bundle
- build_deploy
- build_deploy_status
- build_logs
- build_go_live
- build_teardown
- build_list_capabilities
- build_recommend_integrations
- build_configure_services
- build_doctor
- build_smoke_test
- build_e2e_test
- build_e2e_test_status
- build_list_data_sources
- build_connect_data_source
- build_discover_source
- build_bind_data_source
- build_run_data_source
- build_list_bound_schemas
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.