crosspad-mcp-server
OfficialRelated Servers
Alternatives to crosspad-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that enables Claude Code to communicate with other Claude Code agents over HTTP, allowing users to ask questions about remote codebases or delegate coding tasks.MIT
- AlicenseAqualityDmaintenanceMCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.4779 npm2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets ChatGPT or any MCP client securely delegate coding tasks to a local Claude Code instance, with git checkpointing, approval gates, and structured results. Supports code review, test running, and rollback via simple tool calls.8 npmMIT
- AlicenseAqualityBmaintenanceCode intelligence MCP server for Claude Code providing multi-project code graph, semantic search, session history, knowledge base, and web search.153MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that lets Claude manage long-running development processes across frameworks like Flutter, Next.js, Spring Boot, and Vite, with lifecycle control, log streaming, and hot reload support.1-
- AlicenseAqualityDmaintenanceAn MCP server that enables Claude to orchestrate multiple autonomous Claude Code agents working in parallel across different projects, with tools to dispatch, monitor, and manage their progress.627 npm1MIT
TDQS
Scored across 8 tools
Each tool targets a distinct concern: repo status, build, device enumeration, environment health, runtime snapshot, flashing, toolset visibility, and task lifecycle. No two tools have overlapping responsibilities, and the descriptions reinforce clear boundaries with explicit platform and scope tags.
All names share the consistent `crosspad_` prefix and snake_case format, so the set is easy to scan and predict. However, the pattern is slightly mixed: `crosspad_build` and `crosspad_flash` are verb-like, while `crosspad_devices`, `crosspad_snapshot`, and `crosspad_toolsets` are noun-like resources.
Eight tools is a well-scoped count for a multi-platform development server, with each tool covering a major workflow area and no redundancy. The count sits comfortably in the ideal range, especially given the built-in toolset management for expanding or hiding tools.
Core workflows—repo status, build, device discovery, environment checks, snapshot, flash, and async task management—are covered without dead ends. Minor gaps like direct device reset, app interaction, or trace collection are plausibly deferred to non-core toolsets, so the surface is slightly incomplete but not broken.