FastMCP is a production-oriented Python framework for the Model Context Protocol (MCP). Rather than being a single application, it is a multi-package library stack: `fastmcp_slim` provides the core server/client framework, `fastmcp_remote` bridges remote MCP servers to local stdio, and `fastmcp_tasks` implements SEP-2663 background task execution. The core architecture centers on the `FastMCP` server class, a `Client` class with transport abstraction (stdio, SSE, Streamable HTTP, in-memory), provider-based component registration (local, filesystem, OpenAPI, proxy, skills), composable middleware, transforms, OAuth/OIDC authentication, OpenTelemetry instrumentation, and a CLI for running, installing, deploying, and inspecting servers. Entry points include the `fastmcp` CLI and the Python APIs `FastMCP`, `Client`, `ClientGroup`, `FastMCPApp`, and `TasksExtension`. This is an application framework, not a data/research repository, though it contains information-retrieval components (BM25 and regex tool search), OpenAPI schema conversion machinery, and telemetry utilities that approach data-engineering utility. The codebase demonstrates strong engineering discipline: extensive unit and integration tests, conformance testing against the MCP spec, lazy imports to preserve startup performance, upgrade-guide tests that verify documentation claims, and a transform/middleware system that keeps extensions decoupled from core server logic. External dependencies include the MCP Python SDK, Pydantic, Starlette/ASGI, OpenTelemetry, optional authlib, optional prefab-ui for interactive apps, and an internal `httpx2` fork, which is the most notable maintenance risk in an otherwise current codebase.
MiroThinker is a deep research agent framework designed for complex, multi-step tasks requiring external tool use. The system orchestrates LLM reasoning with a modular suite of MCP (Model Context Protocol) tools including web search, code execution, vision, audio, and reasoning capabilities. It features sophisticated context management through failure experience summarization and sliding window truncation to handle long conversations. The agent iteratively generates tool calls, executes them via MCP servers, and integrates results until producing a final answer. The repository includes benchmark evaluation scripts for GAIA, BrowseComp, HLE, and other research benchmarks, trace collection utilities for model improvement, and a Gradio demo for interactive use. Architecture centers on an orchestrator managing the agent loop, a pipeline for step execution, tool executors handling MCP server interactions, and LLM abstractions supporting Anthropic and OpenAI APIs with prompt caching.
This is a monorepo containing over 40 independent MCP (Model Context Protocol) servers for AWS services, hosted under awslabs/mcp. Each server exposes tools, resources, and prompts that allow AI agents (coding assistants, chatbots) to interact with AWS APIs, databases, documentation, and best practices. The architecture is a collection of standalone Python packages, each with its own entry point (server.py/main.py), tests, Dockerfile, and PyPI distribution. Servers are built using either FastMCP or the lower-level MCP Python SDK, with consistent patterns for read-only enforcement, error handling, AWS client creation, and user-agent tracking. The codebase demonstrates solid engineering with extensive test coverage, but suffers from significant copy-paste boilerplate across servers (healthcheck scripts, Context singletons, test_init.py) and inconsistent use of MCP frameworks. Notable high-craftsmanship components include the AWS API MCP server's custom CLI-to-IR parser and execution engine, the OpenAPI MCP server's pluggable authentication provider framework, and the DynamoDB MCP server's schema-driven code generation tool. The repository is actively maintained with frequent commits and issue triage, though some servers are marked as deprecated or in initial setup, and the announcement of a successor ('Agent Toolkit for AWS') suggests potential future migration.
This is the server platform for the XiaoZhi (小智) ESP32 voice-assistant ecosystem: a large multi-component monorepo that turns low-cost ESP32 hardware into an AI voice assistant. The core is a Python asyncio service (main/xiaozhi-server) that maintains WebSocket connections with devices and runs a real-time audio pipeline — VAD, ASR, intent/LLM orchestration, tool calling, and TTS — streaming audio back to the device. Device onboarding, OTA firmware updates, and the WebSocket handshake are partly in the Python server and partly in a Java Spring Boot management API (main/manager-api) backed by MySQL + Redis, which exposes a broad admin surface: users, devices, agents, model-provider configuration (LLM/ASR/TTS/VAD/memory/intent), RAGFlow-backed knowledge bases, voice clone, voiceprint, chat history, and MCP tool management. Two management frontends exist (a Vue 2 web console and a uni-app/Vue 3 mobile app), plus a Live2D digital-human web client and an offline theme generator for firmware assets. It is an application, not a research repository — no notebooks, data pipelines, or analytical datasets; the 'data' features (RAG ingestion, voice cloning, chat-history reporting, performance testers) are all operational application features.
ChatClaw is a desktop AI assistant application built with Wails v3 (Go backend + Vue 3 frontend) that provides a local-first, multi-platform AI agent experience. It integrates with multiple messaging platforms (WeChat, QQ, DingTalk, Feishu, WeCom, WhatsApp) through gateway adapters and manages AI agents using the CloudWeGo Eino framework. The application features a knowledge base with full-text search (FTS5) and vector embeddings (sqlite-vec), document processing pipeline (parsing, splitting, RAPTOR hierarchical summarization), scheduled tasks with cron execution, a skill marketplace, MCP tool support, and native desktop capabilities like window snapping, floating ball, and text selection popups. It also bundles an OpenClaw Node.js runtime for advanced agent workflows. The frontend is Vue 3 with TypeScript, Pinia, and shadcn-vue UI components. The architecture is a monolith with service-oriented backend and multiple WebView windows. Note: The repo shows signs of hybridity as it includes substantial data/research components (RAPTOR, embeddings, document processing) but these serve the application's core functionality.