Mybatis Mapper2sql

Created By
handsomestWei10 months ago
Automatically extract SQL statements from MyBatis mapper XML files. Support automatic mocking of SQL parameters, and support automatic connection to the database to execute SQL tests and output results.
Overview

what is Mybatis Mapper2sql?

Mybatis Mapper2sql is a tool that automatically extracts SQL statements from MyBatis mapper XML files, enabling efficient SQL testing and analysis.

how to use Mybatis Mapper2sql?

To use Mybatis Mapper2sql, you can run the server with the appropriate command and provide the path to your mapper XML files. The tool will extract SQL statements, mock parameters, and execute tests against a database.

key features of Mybatis Mapper2sql?

  • SQL Extraction: Extracts SQL statements from MyBatis mapper XML files.
  • Parameter Mocking: Automatically generates SQL parameters based on resultMap and JDBC type inference.
  • SQL Testing: Connects to a database to execute SQL and record results.

use cases of Mybatis Mapper2sql?

  1. Extracting SQL for quick analysis and debugging.
  2. Testing SQL statements against a live database to ensure correctness.
  3. Mocking parameters for SQL statements to simulate different scenarios.

FAQ from Mybatis Mapper2sql?

  • Can Mybatis Mapper2sql handle all types of SQL?

Yes! It supports various SQL types as long as they are defined in the MyBatis mapper XML files.

  • Is Mybatis Mapper2sql free to use?

Yes! It is open-source and available for everyone to use.

  • How do I set up Mybatis Mapper2sql?

You need to configure the server with the correct database connection details and run the provided command.

Server Config

{
  "mcpServers": {
    "mapper2sql": {
      "command": "java",
      "args": [
        "-DdbType=mysql",
        "-DjdbcDriver=com.mysql.cj.jdbc.Driver",
        "-DjdbcDriverJar=/path/to/mysql-connector-java-8.0.33.jar",
        "-DjdbcUrl=jdbc:mysql://localhost:3306/testdb",
        "-DuserName=root",
        "-Dpassword=your_password_here",
        "-jar",
        "mapper2sql-mcp-server-1.0.0.jar"
      ],
      "env": {
        "JAVA_HOME": "/path/to/jdk17",
        "PATH": "/path/to/jdk17/bin;${PATH}"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
9 months ago
Author Name
handsomestWei
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago