Search Oryxen

Search tools, jump to categories, and open key destinations

Recorded alternatives

Alternatives to agent-lsp

Every candidate below sits in AI Coding. What ends up on this page is decided entirely by a recorded score — not by bidding, not by editor taste. Review both records, check current vendor terms, then decide.

#1 AI CodingUnknown

bernstein — alternative #1 to agent-lsp

🐍 🏠 ☁️ 🍎 🪟 🐧 - Deterministic multi-agent orchestrator for 37 CLI coding agents (Claude Code, Codex, Cursor, Aider, Gemini CLI, GitHub Copilo...

GitHub source
#2 AI CodingUnknown

m1nd — alternative #2 to agent-lsp

⭐ 22 — Local-first MCP server that gives a CLI coding agent a neuro-symbolic code graph over the repo: impact/why/change-reasoning across a...

GitHub source
#3 AI CodingFree

CLITrigger — alternative #3 to agent-lsp

⭐ 12 — Self-hosted web UI for orchestrating Claude Code, Codex, and Gemini CLIs in parallel git worktrees. Features multi-agent discussion m...

GitHub source14MIT
#4 AI CodingUnknown

oz-mcp-server — alternative #4 to agent-lsp

📇 🏠 🍎 🪟 🐧 - Bridges Warp's Oz coding agent to any IDE or MCP client (Claude Code, Cursor, Codex), plus native @oz in VS Code Copilot Chat. I...

GitHub source3MIT
#5 AI CodingUnknown

postmortemthis — alternative #5 to agent-lsp

⭐ 1 — Runs every coding-agent CLI you have (Claude Code, Codex, Gemini, Qwen, Vibe) in parallel and read-only over your diff, then synthesiz...

GitHub source
#6 AI CodingUnknown

Agentic-MIKE-Plus — alternative #6 to agent-lsp

🐍 🏠 🪟 - MCP server (10 tools) for a headless, natural-language DHI MIKE+ urban-water modelling workflow: model inspection, parameter read/ed...

GitHub source
#7 AI CodingUnknown

agy-bridge — alternative #7 to agent-lsp

📇 🏠 🍎 🪟 🐧 - Delegate heavy tasks from Claude Code (or any MCP client) to the Antigravity CLI (Gemini): file analysis, repo archaeology, web...

GitHub source
#8 AI CodingUnknown

django-orm-lens — alternative #8 to agent-lsp

🐍 🏠 🍎 🪟 🐧 - Django ORM static-analysis MCP server. Nine read-only tools (list_apps, list_models, describe_model, find_relations, cascade_pre...

GitHub source

Questions about this page

How were these alternatives selected?

Each candidate is a live catalogue record in the same primary category, picked by a deterministic score that Oryxen records in its catalogue: how many meaningful words the two listings share, whether their pricing classes oppose (a paid product against a free one), whether both are open source, and whether either record is featured. The same catalogue state always produces the same list — no randomness, no manual ranking.

Are these alternatives ranked by payment?

No. Rows are ordered only by the recorded score, highest first, with alphabetical ties — payment never influences the order, nothing here is paid placement, and Oryxen charges no listing or placement fee.

Always verify current terms with agent-lsp directly — Oryxen records pricing classes, not live quotes.