database_status — Nutrition MCP MCP Tool
database_status
(database status) is one of 14 tools on the
Nutrition MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call database_status from your client
- Claude Code Nutrition MCP database_status run in your project directory
- Claude Desktop Nutrition MCP database_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Nutrition MCP database_status ~/.cursor/mcp.json
- VS Code Nutrition MCP database_status .vscode/mcp.json
- Zed Nutrition MCP database_status ~/.config/zed/settings.json
- Windsurf Nutrition MCP database_status ~/.codeium/windsurf/mcp_config.json
- Cline Nutrition MCP database_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Nutrition MCP database_status ~/.gemini/settings.json
- Grok Nutrition MCP database_status .mcp.json (in your project root)
- ChatGPT Nutrition MCP database_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Nutrition MCP database_status Settings → Connectors → Add custom connector
- LangChain Nutrition MCP database_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nutrition-mcp https://docuslide-mcp-production.up.railway.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.