chubbyskills is a personal knowledge management CLI toolkit that ingests content from over a dozen platforms (YouTube, Bilibili, X, Xiaohongshu, WeChat, Douyin, Podcasts, etc.), transcribes audio/video locally or via cloud providers, and outputs structured Markdown notes with YAML frontmatter (schema v1). The system is architected as a collection of modular "skills" (one per platform) orchestrated by a unified CLI (`tools/chubby.py`), with shared utilities in `chubby_common/`. It includes an incremental knowledge base indexer using SQLite FTS5 and optional semantic embeddings, an MCP server exposing six tools for AI agent integration, and a deterministic evidence brief generator with integrity validation. Operation is local-first: transcription uses SenseVoice and faster-whisper, video downloading uses yt-dlp, and all processing is designed to work offline. Cloud transcription (Atlas/MuAPI) and LLM enrichment (DeepSeek) are optional extensions. The repository also provides a skill installer, platform smoke testing, output validation, and retry mechanisms with credential redaction. Despite the breadth, the codebase maintains clean separation of concerns, with the shared library standing out as a reusable zero-dependency core.
This is a VS Code extension that provides a unified interface for discovering, installing, and managing MCP (Model Context Protocol) servers and AI agent skills. It integrates with multiple sources: the Official MCP Registry, skills.sh, GitHub repositories, and CloudMCP (a hosted alternative). The extension offers a chat participant (`@mcp`) for natural-language search and install, and a sidebar webview with search and management tabs. It supports 30+ AI coding agents including GitHub Copilot, Claude Code, and Codex CLI. The architecture consists of a TypeScript extension backend (using esbuild for bundling) and a React 19 + Vite + Tailwind CSS + shadcn/ui frontend, communicating via typed RPC messages. Telemetry is collected anonymously with standardized error classification. The codebase is well-structured with clear separation of concerns, CI/CD pipelines, and unit tests.
Docfork is a documentation lookup service designed specifically for AI coding agents and developers. It provides up-to-date, version-pinned documentation through a Model Context Protocol (MCP) server with two core tools: `search_docs` for finding relevant documentation sections and `fetch_doc` for retrieving full content. The service is accessed via IDE plugins (Cursor, Claude Code, etc.), a command-line interface (dgrep), and a TypeScript SDK. The architecture features a monorepo structure with separate packages for the MCP server, CLI tool, SDK, and IDE integrations, using Turborepo for build orchestration and pnpm workspaces for package management. Key features include authentication via API keys or OAuth, team-based 'Cabinets' to scope documentation to specific project stacks, and privacy-first telemetry that collects only metadata without querying user data.
GistPad MCP is a Model Context Protocol (MCP) server that provides a comprehensive interface for managing GitHub Gists through AI assistants like GitHub Copilot and Claude Desktop. It exposes tools for CRUD operations on gists, file management within gists, comments, daily notes, archiving, starring, and reusable prompts. The server runs over stdio and uses the GitHub REST API via a custom typed fetch client. It features a caching layer with hourly refresh, resource subscriptions, and change notifications. The codebase is written in modern TypeScript (ES2024, Node.js 22+) with strict type safety, comprehensive tests for the file editing tool, and a clean modular architecture separating concerns into tools, server, store, and utilities. It demonstrates strong engineering practices including abstract base classes for stores, automatic tool annotation derivation, and careful error handling.
Project AIRI is a comprehensive multi-platform AI agent and virtual character platform. It functions as a desktop application (Electron), web interface (Vue.js), and mobile client (Capacitor), centered around an LLM-powered 'brain' that controls 3D avatars (Live2D, VRM, Spine) and interacts with the physical world via computer automation (MCP) and gaming bots (Minecraft). The system integrates speech-to-text, text-to-speech, and vision processing to create a conversational agent capable of real-time interaction. It features a robust backend server (Hono/PostgreSQL) for authentication, billing (Flux currency), and provider routing, alongside a plugin system allowing third-party extensions to inject functionality. Architecturally, it is a large monorepo managed by pnpm and Turbo, separating concerns into apps, packages, services, and plugins. The codebase demonstrates significant engineering effort in managing complex state across Electron IPC, WebSocket communication, and local-first data synchronization. It implements custom concurrency ledgers for billing, GPU resource coordination for model inference, and sandboxed execution environments for AI planning tasks. The system is actively developed with frequent commits and a large plugin ecosystem, though it relies heavily on bleeding-edge dependencies and beta libraries. The platform solves the problem of creating autonomous virtual characters with agency, moving beyond simple chatbots to agents that can control computers, play games, and maintain persistent memory. It exposes a standardized provider registry for AI models and a plugin SDK for extensibility. While the architecture is sophisticated, the reliance on rapidly evolving AI standards (MCP, LLM APIs) and bleeding-edge Node.js versions introduces technical debt and maintenance overhead.
Mistral Vibe is a production-grade terminal-based AI coding agent by Mistral AI. It provides an interactive CLI powered by Textual for multi-turn LLM conversations, file editing, shell execution, and subagent delegation. The system is architected around a core agent loop that orchestrates tool calls with a permission system, session management (resume, rewind, fork), and an event-driven checkpointing mechanism for file state snapshots. It integrates with multiple LLM providers (Mistral, Anthropic, OpenAI, Vertex) via a backend adapter pattern, and supports external integrations through MCP (Model Context Protocol) servers, custom hooks, and a skill system. The codebase heavily employs layered configuration, ports/adapters for audio, notifications, and update checking, and includes an app server for IDE integration via the ACP (Agent Communication Protocol). It also features telemetry via OpenTelemetry and GrowthBook-based experiments. The repository is actively maintained with recent commits, a comprehensive test suite (>1400 tests), and CI/CD pipelines for PyPI releases and PyInstaller binaries.
Mods is a CLI tool that pipes command output to large language models (LLMs) for AI-powered processing. It reads stdin, prepends a user prompt, sends the combined text to an LLM (OpenAI, Anthropic, Cohere, Google, Ollama, etc.), and streams the response to stdout. The architecture is a single Go binary using Bubble Tea for TUI (spinner, viewport) and a plugin-like provider system via the `internal/stream` interface. Key entry points are `main.go` (cobra CLI) and `mods.go` (Bubble Tea model). Data flows: stdin -> prompt assembly -> provider API call -> streaming output -> optional conversation caching (SQLite + gob files). External dependencies include multiple AI SDKs, Bubble Tea, Glamour for Markdown rendering, and SQLite for conversation storage. The repository is now archived as of March 2026, with the team focusing on a successor tool (Crush). Despite being archived, the codebase is well-structured, cleanly separated, and demonstrates strong Go engineering practices with a focus on testability and modularity.
Macro is a large open-source monorepo (AGPLv3) for an all-in-one collaborative productivity platform that unifies email, messaging, documents, tasks, CRM, AI agents, and more. The backend consists of 42+ Rust microservices following a consistent hexagonal architecture (domain/inbound/outbound), with PostgreSQL, OpenSearch, Redis, S3, Kafka/SQS/EventBridge for data storage and event-driven processing. The frontend is a SolidJS single-page application with a heavily customized Lexical editor, block-based content system, real-time collaboration via CRDT (Loro), and Tauri-based desktop/iOS apps. AI is a first-class feature with agent harnesses, MCP integration, and an AI editing worker. Infrastructure is managed via Pulumi and Docker Compose for local development. The codebase demonstrates high engineering craftsmanship with consistent patterns, extensive testing, and comprehensive observability, though the sheer scale and volume of generated code introduce some maintenance overhead.
This Rust codebase is an LLM inference proxy and tool-routing gateway. It exposes an OpenAI-compatible HTTP API (`/v1/chat/completions`, `/v1/models`) and forwards requests to multiple upstream LLM providers (OpenAI, Anthropic via direct/Bedrock, Vertex AI, vLLM DeepSeek, TokenHub) through a unified Provider trait. A QUIC server (s2n-quic, TLS 1.3) accepts connections from serverless tools written in Go or Node.js; the agent loop performs multi-round tool calling, invokes registered tools, and streams results back in SSE format. A separate model API proxy layer handles non-chat endpoint shapes (messages, responses, generateContent) with usage extraction and injection. Architecturally, the system is a Rust CLI binary (`yomo`) with three subcommands: `serve` starts the HTTP API and QUIC zipper, `init` scaffolds serverless tool projects, and `run` launches a tool subprocess and connects it to the zipper. Tool registration is done at runtime over QUIC and stored in-memory, so state is lost on restart. The HTTP layer is Axum, auth is bearer-token, and observability uses OpenTelemetry. The serverless execution model is subprocess-based: it creates temporary directories, runs `npm install`/`go mod tidy`, and exchanges metadata over stdout. Reusable engineering exists in the framing protocol (`io`), streaming SSE mappers, usage aggregation logic, TLS configuration, and provider error separation. However, the provider implementations are duplicated and brittle to upstream API drift; hard-coded model limits, ephemeral tool state, and near-empty serverless stubs reduce long-term maintainability. No integration tests against real upstream APIs were found in the reviewed surface.
Perfetto MCP is a Model Context Protocol server that provides tools for analyzing Perfetto trace files. It maintains persistent connections to trace files and exposes various analysis tools through the MCP protocol, including ANR detection, CPU profiling, jank frame detection, memory leak analysis, and more. The architecture features a modular design with separate components for connection management, tool implementations, and resource registration. Key entry points include the main server module, development entrypoint, and package initialization. The system handles connection lifecycle management with automatic reconnection and provides structured JSON responses for all tool invocations.
This repository is a production-grade, full-stack enterprise AI agent platform developed by iFlytek (Astron Agent). The system allows organizations to create, configure, deploy, and manage conversational AI agents (bots) with advanced workflow automation, knowledge retrieval (multi-strategy RAG), a plugin ecosystem (including MCP and HTTP tools), and multi-tenant team collaboration. The architecture is polyglot and service-oriented: a Java Spring Boot console backend handles bot lifecycle management, publishing to channels (API, WeChat, Feishu, marketplace), RBAC permissions, enterprise spaces, and notification systems. Python FastAPI core services power the workflow engine (20+ node types including LLM, code, decision, memory, knowledge), agent runtime with skill sandbox execution, knowledge indexing and retrieval, and plugin integrations (link server, RPA, MCP). A Go service manages tenant authentication and app key verification. The React + TypeScript frontend provides an interactive console for workflow design, model management, resource management (databases, knowledge bases, skill files), trace logs, and chat interfaces. External dependencies include multiple LLM providers (iFlytek Spark, OpenAI, Anthropic, Google, DeepSeek), MySQL, Redis, Kafka, S3-compatible storage, and Casdoor for SSO. The codebase demonstrates professional engineering with test coverage (JUnit, pytest, Jest), Flyway and Alembic database migrations, CI/CD pipelines, and a modular design using strategy, factory, and AOP patterns. However, it shows signs of complexity from polyglot maintenance, some duplicated frontend components, and legacy credential handling that has been addressed through targeted migration fixes. Overall, it is a well-maintained, actively developed platform suitable for mid-to-large enterprise deployments.
HeadlessX is a self-hosted web scraping and browser automation platform with anti-detection capabilities. It provides a Next.js 16 dashboard, an Express 5 API with Prisma/PostgreSQL, a BullMQ queue worker, and a published CLI. The core value proposition is anti-detection scraping via the headfox-js package (Camoufox-compatible Firefox bundles), fingerprint generation, CAPTCHA solving, and LLM-friendly markdown output. The system supports multiple operators: website scraping/crawling/mapping, Google AI Search, Tavily search, Exa search, and YouTube extraction. It includes sidecar services for HTML-to-Markdown (Go) and YouTube extraction (Python FastAPI). The architecture is a monorepo with Nx orchestration, Docker Compose deployment, and an MCP endpoint for AI assistant integration. External dependencies include Redis, Postgres, Playwright, MaxMind GeoIP, and external APIs (Tavily, Exa, Google). The codebase is well-structured with clear separation of concerns, modern TypeScript, and reusable patterns in both frontend and backend.
This repository is an AI-driven story-to-video production platform. It is a full-stack Django 3.2 backend with Vue 2 frontend, Celery task queue, Redis pub/sub, and Docker deployment. The system ingests user story ideas and orchestrates a multi-stage pipeline: rewrite → storyboard → image generation (text2image/image2video) → camera movement → video generation → Jianying (剪映) draft export. All AI capabilities are consumed via external APIs (OpenAI, ComfyUI, Volcano Engine, etc.) through a pluggable AI client abstraction layer. Key entry points include RESTful APIs (DRF), SSE streaming for real-time progress, MCP (Model Context Protocol) JSON-RPC endpoints for agent integration, and a Vue-based canvas UI for visual workflow editing. The architecture follows a modular Django app pattern with clear separation: core infrastructure (pipeline orchestration, AI clients, Redis streaming), domain apps (projects, prompts, models, workflows, content, agent, MCP), and a frontend SPA. External dependencies include Redis, Celery, MySQL/PostgreSQL, external AI vendor APIs, and optional Jianying draft generation. The codebase demonstrates strong engineering practices with reusable patterns for AI client abstraction, Redis pub/sub streaming, MCP tool registration, and pipeline stage processors, but has notable technical debt: Django 3.2 (EOL), mixed async/gevent, Vue 2 (EOL), and some closed-source compiled components.
LeanKG is a Go-based knowledge graph engine for AI-assisted development. It indexes source code from multi-language repositories into a graph of elements (functions, types, classes) and relationships (calls, imports, implements), stored in SQLite or PostgreSQL with optional vector embeddings for semantic search. The system provides a CLI, REST API, MCP (Model Context Protocol) server, and a React web UI (force-directed graph, file tree, code panel). Core capabilities include incremental indexing with three-signal change detection, a four-tier query ladder (cold/exact/fuzzy/semantic), impact analysis with blast radius, organizational knowledge management (incidents, notes, env reports), ontology matching, federation across servers, and token-budgeted compression for AI tool integration. The architecture is modular: the store backend interface supports SQLite and PostgreSQL with a shared migration ledger; indexing uses regex extractors for 40+ languages with an optional tree-sitter CGO tier; embeddings use a provider abstraction (OpenAI-compatible, llama.cpp sidecar, deterministic). The codebase is well-structured with extensive tests, hermetic test patterns, and deterministic output design. Notable reusability includes the compress package (shell output, git diff), auth token system, store abstraction pattern, and A/B benchmarking harness.
This repository implements an MCP (Model Context Protocol) server that provides semantic code search capabilities for AI assistants. It enables developers to search their codebases by meaning rather than just keywords, using local AI models to ensure privacy and avoid external API calls. The system features semantic code search using embeddings (nomic-embed-text-v1.5 with MRL), incremental indexing with file watching, efficient SQLite-based caching of embeddings, cross-platform package version checking across 20+ ecosystems, workspace switching capabilities, and resource throttling to prevent system overload during indexing. The codebase demonstrates strong engineering practices with proper error handling, modular design, and attention to user experience.
OysterWorkflow is an open-core desktop application (Electron + React) that records a user's computer activity via Screenpipe (screen, audio, UI events), then uses multi-stage LLM calls to extract reusable, structured 'skills' (workflow graphs) that AI agents (Codex, Claude, Hermes) can execute. The system provides a full lifecycle: capture → ingest → normalize → segment → LLM-based workflow discovery → skill extraction → workflow graph generation → quality evaluation → installation into agent skill directories → execution via MCP or Hermes CLI. It also includes a cloud sync layer (Supabase), a marketplace (ClawHub), and a local runtime HTTP server for the UI. Architecturally, it is a hybrid monolith with clear module boundaries: a desktop shell (Electron main process), a local runtime server (Express), a CLI (commander), a React UI (Vite + React Flow), and a product state layer (SQLite-backed with cloud sync). The codebase is TypeScript-first, ESM-only, and heavily tested (200+ test files). It demonstrates strong engineering practices: atomic file I/O, bounded child process management, immutable revision control for workflow graphs, and a sophisticated prompt registry with versioned inheritance. While primarily an application, it contains a significant data pipeline component (ingest → normalize → segment → LLM extraction) that could be considered a research-grade feature engineering system. The repo is actively maintained with frequent commits, CI, and issue triage. Notable risks include heavy sidecar bundling (Screenpipe, Hermes, ffmpeg), rapid prompt set version churn, and a mixed licensing model (Apache 2.0 open core + PolyForm Noncommercial for product code).
This repository is a community-curated awesome list for the Model Context Protocol (MCP) ecosystem, cataloguing hundreds of MCP server implementations, clients, frameworks, utilities, and tutorials. It is primarily a structured markdown documentation site with a consistent badge taxonomy (language, scope, OS), a deep category hierarchy, and multi-language translations. The repo contains no application source code or data pipeline; the only executable logic is a GitHub Actions workflow that validates pull requests adding new entries. The validation enforces formatting standards, allowed emoji tags, Glama badge requirements, duplicate link checks, and non-GitHub URL rejection, which keeps the list high-quality at scale despite its size. The repository serves as a discovery hub for engineers building with LLMs and agentic systems, making it a valuable reference asset rather than a runnable service. It is actively maintained, with recent commits, broad community participation, and a strong automation framework, though its value derives from curation quality rather than software craftsmanship.
TrendRadar is a configurable news aggregation and trend analysis system that crawls hot lists from 11+ Chinese platforms (Zhihu, Weibo, Douyin, Bilibili, etc.) and RSS/Atom feeds, filters content via keyword DSL or AI-based interest matching, performs AI-powered analysis (sentiment, controversy, topic trends), generates rich HTML reports, and pushes notifications to 9+ channels (Feishu, DingTalk, Telegram, Email, ntfy, Bark, Slack, WeCom, generic webhook). It is primarily an application (with CLI entry points, scheduling via timeline.yaml, Docker/GitHub Actions deployment) but incorporates data-pipeline patterns such as multi-stage ETL (crawl → store → filter → analyze → report), SQLite storage with optional S3 remote sync, and AI batch processing. The architecture is a modular monolith: the core `trendradar` package handles all orchestration, while a separate `mcp_server` package exposes 20+ tools via Model Context Protocol (MCP) for LLM integration. The system is heavily config-driven (YAML and text files) and includes a standalone web-based config editor. External dependencies include the third-party newsnow API (for hot lists), LiteLLM (for AI model abstraction), and various notification service APIs. The codebase demonstrates good craftsmanship with clean abstractions (storage backends, notification dispatcher, AI client), though some duplication exists between the core and MCP notification logic, and the extensive configuration surface requires careful maintenance.
Chat2DB is an AI-powered database client and SQL workspace supporting over 40 databases via a plugin architecture. It provides a full-featured SQL editor with syntax highlighting, autocompletion, and execution, along with database metadata browsing, data import/export, BI dashboards, and an AI assistant that can generate SQL, explain queries, and create charts. The system is designed as a hybrid desktop/web application, with a React/TypeScript frontend (using Ant Design, Monaco Editor, Zustand for state management) and a Java Spring Boot backend with a layered domain model. The desktop version uses JCEF (Chromium Embedded Framework) for native integration, while the web version runs as a standalone server. Database support is modular via SPI plugins, each providing metadata, SQL builders, value processors, and completion logic. The architecture is centered around a plugin system where each database type implements interfaces like IPlugin, IDbMetaData, and IDbManager, enabling extensible multi-database support. The frontend uses Zustand stores with slice-based state management, and the backend provides REST APIs for SQL execution, AI chat, and data management. Key entry points include the frontend main page (CommunityMainPage), backend controllers (e.g., DbSqlController, AiChatController), and plugin registration via META-INF/services. Data flows involve SQL execution requests from the editor to the backend, which delegates to the appropriate database plugin and returns results asynchronously with streaming support for AI and large result sets. External dependencies include Java/Spring Boot, React, Monaco Editor, ANTLR for SQL parsing, ECharts for charts, and various JDBC drivers for database connectivity. The system also integrates with AI model APIs (e.g., OpenAI, Claude) via configurable endpoints. The codebase demonstrates a strong separation of concerns through its SPI plugin pattern and state management slices, though it exhibits some duplication across database plugins and has limited test coverage.
PraisonAI is a production-oriented, multi-language AI agent orchestration framework shipped as a monorepo of cooperating Python, TypeScript, and Rust packages. The core SDK (`praisonaiagents`) implements `Agent`, `Task`, `AgentTeam`, and `AgentFlow`/`Workflow` abstractions with MCP support (stdio/HTTP/WebSocket/SSE), integration with 20+ LLM providers via LiteLLM-style configuration, memory backends (SQLite, file, mem0, MongoDB), RAG/knowledge bases over vector stores, guardrails, approval flows, policy engines, context compaction, telemetry, background jobs, and durable run ledgers. A user-facing `praisonai` wrapper provides a Typer CLI (`run`, `chat`, `code`, `serve mcp`, agent-as-API), bot adapters for Telegram/Discord/Slack via a WebSocket gateway, sandboxed compute (Docker, E2B, Modal, Daytona), deployment registries, cloud managed agents, and a fine-tuning package (`praisonai-train`). The repository is decisively an application/framework, though it carries data-research features as part of the product surface (RAG pipelines, evaluation loops, synthetic-data generation, LoRA fine-tuning), making it a hybrid in feature terms only.