get_state — OpenFile MCP Tool Read-only
get_state
(get state) 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 get_state from your client
- Claude Code OpenFile get_state run in your project directory
- Claude Desktop OpenFile get_state ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor OpenFile get_state ~/.cursor/mcp.json
- VS Code OpenFile get_state .vscode/mcp.json
- Zed OpenFile get_state ~/.config/zed/settings.json
- Windsurf OpenFile get_state ~/.codeium/windsurf/mcp_config.json
- Cline OpenFile get_state ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI OpenFile get_state ~/.gemini/settings.json
- Grok OpenFile get_state .mcp.json (in your project root)
- ChatGPT OpenFile get_state Settings → Connectors → Advanced → Developer mode
- Claude.ai OpenFile get_state Settings → Connectors → Add custom connector
- LangChain OpenFile get_state 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
- list_states
- 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.