FleetQ
Related Servers
Alternatives to FleetQ
- MIT
- FlicenseNot gradedqualityDmaintenanceExposes LangChain agent capabilities through the Model Context Protocol, enabling multi-step reasoning tasks with ReAct pattern execution via a production-ready FastAPI service deployed on Google Cloud Run.11 npm4-
Related Servers
- AlicenseNot gradedqualityAmaintenanceOpen-source AI teammates for your company. The self-hosted agent layer: build, run and govern AI agents on your own servers, models and rules. RAG, skills, a real browser, 4,700+ MCP servers and an API, with budgets, approvals and an audit trail. Apache-2.0, built on Pydantic AI.249Apache 2.0

agent-taskofficial
FlicenseNot gradedqualityCmaintenanceAgentTask is a governed work platform where human teams and AI agents share one backlog. Hosted remote MCP server (streamable HTTP, OAuth 2.1 or org API keys) with 60+ tools for tasks, subtasks, projects, groups, labels, notes, comments, attachments, search, crews, and agent runs.-- AlicenseNot gradedqualityDmaintenanceA control plane for AI agents and human supervisors. Persistent task registry with scoped permissions, inter-agent delegation, and full provenance — all accessible via MCP. Deploy on Supabase free tier in 3 commands.43 npm11Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables external MCP clients like Claude Desktop, Claude Code, Cursor and Zed to hand work to a local crew of AI agents that plan, write, check and fix code in a folder, while also acting as an MCP client that can use their tools. Runs locally with user-supplied keys, approval-gated commands, diffable and undoable runs.AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceA local-first mission control for AI agent harnesses, providing a unified MCP gateway for shared memory, task queue, and encrypted secrets across multiple agents.2 npm2MIT

SideButtonofficial
AlicenseNot gradedqualityBmaintenanceOpen source AI agent platform with MCP server, browser automation, knowledge packs, and workflow engine. Works with Claude Code, ChatGPT, Cursor, and any MCP client.20 npm6Apache 2.0
TDQS
Scored across 34 tools
Each tool targets a distinct domain or entity (e.g., agents, approvals, credentials, experiments, signals). Even related tools like signal_connectors and signal_manage have clearly separated responsibilities (setup vs. operation). Descriptions and action lists further clarify boundaries, leaving no ambiguity.
Most tools follow a consistent <noun>_manage pattern (e.g., agent_manage, credential_manage). Minor deviations exist: integration_execute, signal_connectors, and workflow_graph break the pattern but remain descriptive and predictable.
With 34 tools, the server feels overloaded. While the platform is broad, many tools (e.g., boruna_manage, evolution_manage) are niche. The count exceeds the 'well-scoped' range and may overwhelm agents, though each tool serves a distinct purpose.
The tool surface covers the platform's major domains comprehensively: CRUD for core entities, lifecycle management, actions for special operations, and many auxiliary features. Minor gaps exist (e.g., no dedicated reporting tool), but overall the surface is robust.