SQLite-Anet-MCP Server

Created By
marekkucaka year ago
SQLite-Anet-MCP Server A blazing-fast, Rust-powered SQLite server for AI agents—speak JSON-RPC, store insights, and manage your database like a pro.
Overview

What is SQLite-Anet-MCP?

SQLite-Anet-MCP is a Rust-powered server that provides SQLite database capabilities via the Model Control Protocol (MCP). It allows AI agents to create, manage, and query SQLite databases efficiently.

How to use SQLite-Anet-MCP?

To use SQLite-Anet-MCP, clone the repository, configure your environment, and run the server. You can interact with the server using JSON-RPC commands to manage your database.

Key features of SQLite-Anet-MCP?

  • Create and manage SQLite database tables
  • Execute SELECT, INSERT, UPDATE, and DELETE queries
  • Describe table schemas and list available tables
  • Save and synthesize business insights from data
  • JSON-RPC 2.0 compatible API
  • Asynchronous request handling with Tokio

Use cases of SQLite-Anet-MCP?

  1. AI agents managing customer databases
  2. Data analysis and insights generation for businesses
  3. Integration with other applications requiring database capabilities

FAQ from SQLite-Anet-MCP?

  • What programming language is used for SQLite-Anet-MCP?

SQLite-Anet-MCP is built using Rust.

  • Is there a requirement for a NATS server?

Yes, a NATS server is required to run the SQLite-Anet-MCP server.

  • Can I run multiple instances of the server?

Yes, you can run multiple instances by configuring different database paths and NATS subjects.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
marekkucak
Star
0
Language
Rust
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago