get_state — valem MCP Tool Read-only
get_state
(get state) is one of 27 tools on the
valem
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 valem get_state run in your project directory
- Claude Desktop valem get_state ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor valem get_state ~/.cursor/mcp.json
- VS Code valem get_state .vscode/mcp.json
- Zed valem get_state ~/.config/zed/settings.json
- Windsurf valem get_state ~/.codeium/windsurf/mcp_config.json
- Cline valem get_state ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI valem get_state ~/.gemini/settings.json
- Grok valem get_state .mcp.json (in your project root)
- ChatGPT valem get_state Settings → Connectors → Advanced → Developer mode
- Claude.ai valem get_state Settings → Connectors → Add custom connector
- LangChain valem get_state pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http valem https://valem.run/mcpOther tools on this server
- list_models
- create_model
- get_model_info
- get_spec
- get_library
- get_field
- mutate
- patch_model
- get_effective_schema
- snapshot
- restore
- explain
- get_history
- get_audit
- verify_audit
- upload_blob
- download_blob
- evolve_spec
- delete_model
- get_view
- get_domain_guidance
- validate_spec
- eval_expression
- test_spec
- dry_run
- pair_browser
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.