QuapQuap

quap-mcp for AI editors

Give Cursor, Claude Desktop and other MCP clients Quap's 29 data tools — running locally.

quap-mcp is a Model Context Protocol server that ships with Quap. It lets AI coding tools such as Cursor and Claude Desktop use Quap's engine: format and validate JSON, convert formats, translate SQL dialects, generate code, mask and analyse data, and run every operation of Quap's AI assistant. It runs on your computer and works on Free.

Set it up

Turn it on

Click MCP in Quap's title bar so it shows as on (MCP is on: clients like Cursor or Claude Desktop can use Quap's tools).

Copy the config

Click ⧉ next to MCP. Quap copies an mcpServers entry with the real path to quap-mcp filled in.

Paste it into your client

Add the entry to your client's MCP settings (see below) and restart the client once.

The copied entry looks like this:

{
  "mcpServers": {
    "quap": {
      "command": "/path/to/quap-mcp",
      "args": []
    }
  }
}

Add the entry to ~/.cursor/mcp.json for all projects, or to .cursor/mcp.json inside one project (Cursor's MCP settings page opens the global file for you). Paste the quap entry inside mcpServers.

Turning it off

Click MCP again. The switch takes effect immediately, without restarting the client: while it is off, the client sees no Quap tools and calls return an explanation.

What clients can do

Examples of requests in Cursor or Claude once Quap is connected:

  • "Validate fixtures/orders.json with Quap and fix the errors."
  • "Convert this YAML config to JSON."
  • "Translate this T-SQL query to PostgreSQL."
  • "Generate C# classes for this API response."
  • "Mask the emails in this sample before I paste it into the ticket."
  • "Group these orders by city and give me the totals."

The full list of 29 tools with descriptions is in the MCP tools reference.

quap-mcp runs locally as a child process of your client. Data you pass to it is processed on your computer. What your AI client sends to its own model is up to the client.

Accent color