conflicts — Assertion Memory MCP Tool
conflicts
(conflicts) is one of 9 tools on the
Assertion Memory
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call conflicts from your client
- Claude Code Assertion Memory conflicts run in your project directory
- Claude Desktop Assertion Memory conflicts ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Assertion Memory conflicts ~/.cursor/mcp.json
- VS Code Assertion Memory conflicts .vscode/mcp.json
- Zed Assertion Memory conflicts ~/.config/zed/settings.json
- Windsurf Assertion Memory conflicts ~/.codeium/windsurf/mcp_config.json
- Cline Assertion Memory conflicts ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Assertion Memory conflicts ~/.gemini/settings.json
- Grok Assertion Memory conflicts .mcp.json (in your project root)
- ChatGPT Assertion Memory conflicts Settings → Connectors → Advanced → Developer mode
- Claude.ai Assertion Memory conflicts Settings → Connectors → Add custom connector
- LangChain Assertion Memory conflicts pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http assertion https://memory.assertion-ai.com/memory/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 25 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.