remember — Miso MCP Tool
remember
(remember) is one of 41 tools on the
Miso
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call remember from your client
- Claude Code Miso remember run in your project directory
- Claude Desktop Miso remember ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Miso remember ~/.cursor/mcp.json
- VS Code Miso remember .vscode/mcp.json
- Zed Miso remember ~/.config/zed/settings.json
- Windsurf Miso remember ~/.codeium/windsurf/mcp_config.json
- Cline Miso remember ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Miso remember ~/.gemini/settings.json
- Grok Miso remember .mcp.json (in your project root)
- ChatGPT Miso remember Settings → Connectors → Advanced → Developer mode
- Claude.ai Miso remember Settings → Connectors → Add custom connector
- LangChain Miso remember pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http miso https://gateway.pipeworx.io/miso/mcp
Other tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- recall
- forget
- miso_fuel_mix
- miso_lmp
- miso_binding_constraints
- miso_load
- miso_wind_solar
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.