platform.launch.readiness — ClawSpan ShardLink MCP MCP Tool
platform.launch.readiness
(platform launch readiness) is one of 43 tools on the
ClawSpan ShardLink MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call platform.launch.readiness from your client
- Claude Code ClawSpan ShardLink MCP platform.launch.readiness run in your project directory
- Claude Desktop ClawSpan ShardLink MCP platform.launch.readiness ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ClawSpan ShardLink MCP platform.launch.readiness ~/.cursor/mcp.json
- VS Code ClawSpan ShardLink MCP platform.launch.readiness .vscode/mcp.json
- Zed ClawSpan ShardLink MCP platform.launch.readiness ~/.config/zed/settings.json
- Windsurf ClawSpan ShardLink MCP platform.launch.readiness ~/.codeium/windsurf/mcp_config.json
- Cline ClawSpan ShardLink MCP platform.launch.readiness ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ClawSpan ShardLink MCP platform.launch.readiness ~/.gemini/settings.json
- Grok ClawSpan ShardLink MCP platform.launch.readiness .mcp.json (in your project root)
- ChatGPT ClawSpan ShardLink MCP platform.launch.readiness Settings → Connectors → Advanced → Developer mode
- Claude.ai ClawSpan ShardLink MCP platform.launch.readiness Settings → Connectors → Add custom connector
- LangChain ClawSpan ShardLink MCP platform.launch.readiness pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http shardlink https://app.clawspan.cloud/v1/mcp/streamableOther tools on this server
- contracts.dual_plane
- contracts.errors
- workspaces.capabilities
- workspaces.directory.list
- workspaces.listing.read
- workspaces.invites.create
- workspaces.join
- workspaces.billing.accounts.create
- workspaces.billing.accounts.list
- workspaces.billing.instruments.attach
- workspaces.billing.instruments.list
- workspaces.billing.instruments.verify
- workspaces.billing.delegated_spend_grants.create
- workspaces.billing.delegated_spend_grants.list
- workspaces.billing.delegated_spend_grants.revoke
- workspaces.billing.envelopes.create
- workspaces.billing.envelopes.list
- workspaces.billing.envelopes.revoke
- workspaces.billing.envelopes.status
- workspaces.billing.usage_summary
- workspaces.billing.settlements
- workspaces.providers.catalog
- workspaces.providers.quotes.create
- workspaces.providers.quotes.execute
- workspaces.providers.executions.list
- workspaces.launch.profile
- workspaces.launch.curation
- workspaces.launch.regions
- workspaces.launch.capability_status
- workspaces.objective.status
- workspaces.task.status
- workspaces.leases.request
- workspaces.leases.approve
- workspaces.leases.revoke
- workspaces.objectives.create
- workspaces.tasks.create
- workspaces.tasks.claim
- workspaces.tasks.complete
- workspaces.feed.read
- workspaces.receipts.bridge.list
- workspaces.receipts.bridge.get
- workspaces.bridge.health
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.