Tokenlite Mysql Mcp
Let your coding agent run read/write SQL against a MySQL database with guardrails instead of pasting credentials into one-off scripts.
Overview
Tokenlite MySQL MCP is a MCP server for the Build phase that gives coding agents guarded, environment-configured access to a MySQL database over stdio.
What is this MCP server?
- stdio MCP package @andezdev/tokenlite-mysql-mcp v4.1.0 with DB_HOST, DB_PORT, DB_USER, DB_PASSWORD, DB_NAME env configur
- EXPLAIN-based guardrails via MCP_EXPLAIN_MAX_SCAN_ROWS to block risky unindexed full table scans (default 1000 estimated
- Positioned as secure, efficient, and intelligent MySQL access for Model Context Protocol clients
- Required DB_NAME plus optional connection defaults (localhost:3306, root user)
- MCP server integration—not a SQL tutorial skill or hosted database product
- Server version 4.1.0 on npm as @andezdev/tokenlite-mysql-mcp
- Default MCP_EXPLAIN_MAX_SCAN_ROWS guardrail of 1000 estimated rows
- Default MySQL port 3306 and host localhost when env vars omitted
What problem does it solve?
Agents cannot safely explore or fix MySQL-backed features when every query requires manual CLI work and there is no protocol-level guard against expensive scans.
Who is it for?
Indie builders with an existing MySQL database who want Claude Code or Cursor to run schema-aware SQL during backend and integration work.
Skip if: Teams that need a managed hosted database, non-MySQL engines only, or production change management without local credentials and review.
What do I get? / Deliverables
After you register the server, your agent can query and work with your MySQL schema using MCP tools and optional EXPLAIN limits that reduce accidental full-table load.
- Agent-callable MCP tools against your MySQL database
- Configurable connection and EXPLAIN scan-row limits
- Repeatable local dev workflow without sharing raw passwords in chat
Recommended MCP Servers
Journey fit
Database access is wired during product build when you connect backends, migrations, and agent tooling to live data. integrations is the canonical shelf for MCP bridges that expose external systems—in this case MySQL—to Claude Code, Cursor, and similar agents.
How it compares
MCP database integration with query guardrails, not a migration framework or ORM code generator.
Common Questions / FAQ
Who is Tokenlite MySQL MCP for?
Solo and small-team developers who already use MySQL and want their AI agent to read and manipulate data through MCP instead of external SQL clients.
When should I use Tokenlite MySQL MCP?
Use it during build and integration work when you need the agent to inspect tables, debug queries, or prototype data changes against a configured DB_NAME.
How do I add Tokenlite MySQL MCP to my agent?
Install @andezdev/tokenlite-mysql-mcp, set DB_NAME (required) and connection env vars, mark DB_PASSWORD as secret, add the stdio server entry in your agent MCP config, and tune MCP_EXPLAIN_MAX_SCAN_ROWS if needed.