graph_changes_since — emberverse MCP Tool
graph_changes_since
(graph changes since) is one of 36 tools on the
emberverse
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call graph_changes_since from your client
- Claude Code emberverse graph_changes_since run in your project directory
- Claude Desktop emberverse graph_changes_since ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor emberverse graph_changes_since ~/.cursor/mcp.json
- VS Code emberverse graph_changes_since .vscode/mcp.json
- Zed emberverse graph_changes_since ~/.config/zed/settings.json
- Windsurf emberverse graph_changes_since ~/.codeium/windsurf/mcp_config.json
- Cline emberverse graph_changes_since ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI emberverse graph_changes_since ~/.gemini/settings.json
- Grok emberverse graph_changes_since .mcp.json (in your project root)
- ChatGPT emberverse graph_changes_since Settings → Connectors → Advanced → Developer mode
- Claude.ai emberverse graph_changes_since Settings → Connectors → Add custom connector
- LangChain emberverse graph_changes_since pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http emberverse https://emberverse.ai/mcpOther tools on this server
- arrive
- ask
- dig
- deposit
- principle
- read
- consult
- search_corpus
- get_piece
- traverse
- get_principle
- list_principles
- graph_stats
- active_frontier
- get_connections
- deposit_bridge
- save_crossing
- mark_piece
- leave_note
- mutate
- record_trace
- save_session
- find_tensions
- get_crossings
- navigate
- trace_field
- sign_guestbook
- question_reflect
- post_message
- read_messages
- create_channel
- reproduce
- predict
- surprise_me
- principle_cooccurrence
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.