Skip to main content

NapCat

Modern protocol-side framework based on NTQQ for building QQ bots

Key Features

NapCat provides a comprehensive framework for building QQ bots with modern architecture and extensive functionality.

OneBot 11 Protocol

Full implementation of the OneBot 11 standard for seamless bot integration

Multiple Adapters

Support for HTTP, WebSocket, and reverse WebSocket connections

Built-in WebUI

Management interface for monitoring and configuring your bot

Native Packet Handling

Low-level packet inspection and manipulation capabilities

Plugin System

Extensible architecture for custom functionality

Database Support

SQLite integration for data persistence and querying

Quick Navigation

Getting Started

Get up and running with NapCat in minutes

Core Concepts

Understand the framework architecture

Configuration

Configure NapCat for your needs

API Reference

Explore the complete API documentation

Guides

Follow step-by-step deployment guides

Community

Join the NapCat community

Why NapCat?

NapCat provides a straightforward setup process and intuitive APIs, making it accessible for beginners while offering powerful features for advanced users.
Optimized for performance, NapCat runs smoothly even on low-resource systems with minimal memory footprint.
Comprehensive implementation of the OneBot 11 standard plus extended APIs for advanced bot functionality.
Actively maintained with continuous development, bug fixes, and feature updates from the community.

What You’ll Learn

This documentation covers everything you need to build and deploy QQ bots with NapCat:
  • Installation: Set up NapCat in different environments (Shell and Framework modes)
  • Configuration: Configure network adapters, login methods, and bot behavior
  • API Usage: Send messages, manage groups, handle events, and more
  • Advanced Features: Packet inspection, database access, custom adapters, and plugins
  • Deployment: Best practices for production deployments
NapCat is a non-profit project. For integration issues, basic questions, or underlying framework issues, please search for solutions on your own — the project community does not provide such support.

Build docs developers (and LLMs) love