Dataxplan Mcp

io.github.arikanatakanPublished by GitHub account arikanatakanv0.1.0Updated Oct 25, 2026

Read PostgreSQL EXPLAIN plans for AI agents: bottlenecks, estimation errors, fixes, charts.

VerifiedSTDIODesktop onlyDatabases

Overview

AI-generated overview

A local MCP server that lets an AI assistant read PostgreSQL EXPLAIN plans and surface bottlenecks, estimation errors, fixes and charts.

What you can do
Read PostgreSQL EXPLAIN plans and identify performance bottlenecks in queries. Point out estimation errors between planned and actual row counts. Suggest fixes for the problems found. Produce charts that visualize the plan.
When to use it
Useful when you are tuning slow PostgreSQL queries and want an assistant to interpret EXPLAIN output, explain where the planner went wrong, and propose concrete improvements.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package dataxplan-mcp over stdio. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
No credentials or secrets are declared, but the server reads query plans, which can expose table names, column names and data distribution details; check what plan text you share with the assistant.

Installation

In SourceWeft

  1. Open Dataxplan Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.