data_api_status — Layero MCP Tool
data_api_status
(data api status) is one of 35 tools on the
Layero
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call data_api_status from your client
- Claude Code Layero data_api_status run in your project directory
- Claude Desktop Layero data_api_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Layero data_api_status ~/.cursor/mcp.json
- VS Code Layero data_api_status .vscode/mcp.json
- Zed Layero data_api_status ~/.config/zed/settings.json
- Windsurf Layero data_api_status ~/.codeium/windsurf/mcp_config.json
- Cline Layero data_api_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Layero data_api_status ~/.gemini/settings.json
- Grok Layero data_api_status .mcp.json (in your project root)
- ChatGPT Layero data_api_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Layero data_api_status Settings → Connectors → Add custom connector
- LangChain Layero data_api_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http layero https://mcp.layero.ru/mcp
Other tools on this server
- search_docs
- whoami
- my_projects
- list_sources
- import_repo
- list_environments
- project_create
- site_status
- env_vars
- project_settings
- connect_analytics
- site_analytics
- check_performance
- connect_domain
- check_domain
- list_domains
- read_site
- site_screenshot
- site_issues
- refactor_site
- check_copy
- list_deploys
- rollback
- retry_deploy
- cancel_deploy
- deploy_logs
- diagnose_deploy
- publish_site
- publish_landing
- data_api_methods
- data_api_grant
- data_api_keys
- data_api_origins
- data_api_probe
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.