isone_lmp — Iso Ne MCP Tool
isone_lmp
(isone lmp) is one of 39 tools on the
Iso Ne
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call isone_lmp from your client
- Claude Code Iso Ne isone_lmp run in your project directory
- Claude Desktop Iso Ne isone_lmp ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Iso Ne isone_lmp ~/.cursor/mcp.json
- VS Code Iso Ne isone_lmp .vscode/mcp.json
- Zed Iso Ne isone_lmp ~/.config/zed/settings.json
- Windsurf Iso Ne isone_lmp ~/.codeium/windsurf/mcp_config.json
- Cline Iso Ne isone_lmp ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Iso Ne isone_lmp ~/.gemini/settings.json
- Grok Iso Ne isone_lmp .mcp.json (in your project root)
- ChatGPT Iso Ne isone_lmp Settings → Connectors → Advanced → Developer mode
- Claude.ai Iso Ne isone_lmp Settings → Connectors → Add custom connector
- LangChain Iso Ne isone_lmp pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http iso-ne https://gateway.pipeworx.io/iso-ne/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
- remember
- recall
- forget
- isone_load
- isone_fuel_mix
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.