list_states — OpenFile MCP Tool Read-only
list_states
(list states) is one of 27 tools on the
OpenFile
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_states from your client
- Claude Code OpenFile list_states run in your project directory
- Claude Desktop OpenFile list_states ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor OpenFile list_states ~/.cursor/mcp.json
- VS Code OpenFile list_states .vscode/mcp.json
- Zed OpenFile list_states ~/.config/zed/settings.json
- Windsurf OpenFile list_states ~/.codeium/windsurf/mcp_config.json
- Cline OpenFile list_states ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI OpenFile list_states ~/.gemini/settings.json
- Grok OpenFile list_states .mcp.json (in your project root)
- ChatGPT OpenFile list_states Settings → Connectors → Advanced → Developer mode
- Claude.ai OpenFile list_states Settings → Connectors → Add custom connector
- LangChain OpenFile list_states pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http openfile https://mcp.joinopenfile.comOther tools on this server
- search_docs
- read_doc
- plan_task
- get_pricing
- quote_application
- list_classes
- suggest_classes
- screen_mark
- search_marks
- suggest_alternatives
- check_site
- read_site
- list_filing_types
- get_filing_type
- create_application
- get_application
- update_application
- get_state
- list_services
- quote_formation
- create_formation
- get_formation
- update_formation
- get_order
- get_filing
- add_specimen
This list was read from the server itself, by connecting to it and calling tools/list on 11 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.