get_next_observation — SkoIA Parts MCP Tool Read-only
get_next_observation
(get next observation) is one of 15 tools on the
SkoIA Parts
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_next_observation from your client
- Claude Code SkoIA Parts get_next_observation run in your project directory
- Claude Desktop SkoIA Parts get_next_observation ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SkoIA Parts get_next_observation ~/.cursor/mcp.json
- VS Code SkoIA Parts get_next_observation .vscode/mcp.json
- Zed SkoIA Parts get_next_observation ~/.config/zed/settings.json
- Windsurf SkoIA Parts get_next_observation ~/.codeium/windsurf/mcp_config.json
- Cline SkoIA Parts get_next_observation ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SkoIA Parts get_next_observation ~/.gemini/settings.json
- Grok SkoIA Parts get_next_observation .mcp.json (in your project root)
- ChatGPT SkoIA Parts get_next_observation Settings → Connectors → Advanced → Developer mode
- Claude.ai SkoIA Parts get_next_observation Settings → Connectors → Add custom connector
- LangChain SkoIA Parts get_next_observation pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http skoia-parts https://parts.skoia.me/mcpOther tools on this server
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.