get_engine_status_resource — Neotic MCP Resource

get_engine_status_resource is one of 1 resource on the Neotic MCP server. Connect the server and your client can attach it as context.

by client

How to attach get_engine_status_resource from your client

• Claude Code Neotic Resource/get_engine_status_resource run in your project directory
• Claude Desktop Neotic Resource/get_engine_status_resource ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Neotic Resource/get_engine_status_resource ~/.cursor/mcp.json
• VS Code Neotic Resource/get_engine_status_resource .vscode/mcp.json
• Zed Neotic Resource/get_engine_status_resource ~/.config/zed/settings.json
• Windsurf Neotic Resource/get_engine_status_resource ~/.codeium/windsurf/mcp_config.json
• Cline Neotic Resource/get_engine_status_resource ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Neotic Resource/get_engine_status_resource ~/.gemini/settings.json
• Grok Neotic Resource/get_engine_status_resource .mcp.json (in your project root)
• ChatGPT Neotic Resource/get_engine_status_resource Settings → Connectors → Advanced → Developer mode
• Claude.ai Neotic Resource/get_engine_status_resource Settings → Connectors → Add custom connector
• LangChain Neotic Resource/get_engine_status_resource pip install langchain-mcp-adapters

Neotic also offers 3 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.