AOI OpenAPI Specification — AOI — Environmental Intelligence for AI Agents MCP Resource
AOI OpenAPI Specification
is one of 5 resources on the
AOI — Environmental Intelligence for AI Agents
MCP server. Connect the server and your client can attach it as context.
by client
How to attach AOI OpenAPI Specification from your client
- Claude Code AOI — Environmental Intelligence for AI Agents Resource/AOI OpenAPI Specification run in your project directory
- Claude Desktop AOI — Environmental Intelligence for AI Agents Resource/AOI OpenAPI Specification ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AOI — Environmental Intelligence for AI Agents Resource/AOI OpenAPI Specification ~/.cursor/mcp.json
- VS Code AOI — Environmental Intelligence for AI Agents Resource/AOI OpenAPI Specification .vscode/mcp.json
- Zed AOI — Environmental Intelligence for AI Agents Resource/AOI OpenAPI Specification ~/.config/zed/settings.json
- Windsurf AOI — Environmental Intelligence for AI Agents Resource/AOI OpenAPI Specification ~/.codeium/windsurf/mcp_config.json
- Cline AOI — Environmental Intelligence for AI Agents Resource/AOI OpenAPI Specification ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AOI — Environmental Intelligence for AI Agents Resource/AOI OpenAPI Specification ~/.gemini/settings.json
- Grok AOI — Environmental Intelligence for AI Agents Resource/AOI OpenAPI Specification .mcp.json (in your project root)
- ChatGPT AOI — Environmental Intelligence for AI Agents Resource/AOI OpenAPI Specification Settings → Connectors → Advanced → Developer mode
- Claude.ai AOI — Environmental Intelligence for AI Agents Resource/AOI OpenAPI Specification Settings → Connectors → Add custom connector
- LangChain AOI — Environmental Intelligence for AI Agents Resource/AOI OpenAPI Specification pip install langchain-mcp-adapters
Other resources on this server
AOI — Environmental Intelligence for AI Agents also offers 4 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 14 November 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.