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