Octopus MCP Server
Related Servers
Alternatives to Octopus MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for reviewing code changes using LLMs, supporting Copilot, Ollama, and OpenAI-compatible endpoints.MIT
- AlicenseBqualityCmaintenanceAI-powered code review server that analyzes git diffs and PRs with context from project guidelines and task lists. Supports integration with Claude Code and Cursor via MCP.3MIT
- AlicenseBqualityBmaintenanceMCP server connecting Claude/Cursor to Codex CLI, enabling code analysis via @ file references, multi-turn conversations, sandboxed edits, and structured change mode.13194 npm24MIT

ThinkReview MCPofficial
AlicenseNot gradedqualityAmaintenanceHosted MCP server that enables AI code reviews on GitHub, GitLab, Azure DevOps, and Bitbucket PR/MR URLs via a single tool (review_url_code), integrating with Cursor, Claude Code, Claude Desktop, and GitHub Copilot through OAuth or Bearer token authentication.1MIT- AlicenseNot gradedqualityDmaintenanceMCP server for automated code review using AI agents. It analyzes code diffs or file paths for bugs, security issues, and style violations.MIT
- FlicenseNot gradedqualityFmaintenanceMCP server for code review using OpenRouter API. Supports local code review via MCP or web interface.12-
TDQS
Scored across 3 tools
Each tool handles a clearly distinct responsibility: verifying connectivity, reviewing a diff, and asking follow-up questions. There is zero overlap that could cause an agent to select the wrong tool.
All tools follow the same snake_case convention with the `octopus_` prefix, creating a predictable pattern. The verb-like suffixes (`status`, `review_changes`, `ask`) are consistent in style and clearly convey action.
At 3 tools, the server is at the minimal end of the ideal range, yet each tool genuinely earns its place and the count is well-scoped for the server's purpose. A couple of additional tools (e.g., configuration or history browsing) could make it feel more substantial.
The core workflow of connect → review → ask follow-ups is fully covered. Minor gaps include the lack of a direct way to list past reviews without using `octopus_ask` and no configuration or preference settings, but these are workable for common use cases.