mcp-server

A small set of MCP server binaries (configured via stdio) that provide tools for specific tasks: text-to-SQL against a MySQL database, retrieving from a Dify knowledge base/dataset, and performing data conversion via a separate command.

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ DevTools mcp stdio text2sql dify retrieval data-conversion go

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Security guidance is minimal in the provided README. It demonstrates passing sensitive values via env and includes a DB connection string in plain text. No TLS requirement, secret-handling best practices, authorization model, or scope granularity are documented. Rate limits and safe-usage/error handling guidance are not described.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want lightweight local MCP tools integrated into an agent framework (e.g., via stdio) and you can provide the necessary environment variables (DB connection string, Dify endpoint/key).

Avoid When

You cannot securely manage credentials or you require strict documentation of tool schemas, error codes, rate limits, and idempotency semantics.

Use Cases

• Natural-language to SQL generation for a MySQL database (via text2sql)
• Knowledge base retrieval from Dify datasets for RAG-style workflows (via dify retriever)
• Converting data between formats/systems (via dt/data_transfer)

Not For

• Production-grade, fully secured multi-tenant deployments without additional hardening and monitoring
• Use cases requiring well-documented, stable public APIs/SDKs and clear operational guarantees

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: Environment-variable based configuration (e.g., DIFY_DATASET_API_KEY) Direct database connection string supplied via env (for text2sql example)

OAuth: No Scopes: No

Authentication/authorization is not described in the README beyond passing credentials (DB link, Dify API key) via environment variables.

Pricing

Free tier: No

Requires CC: No

No pricing information provided; appears to be self-hosted binaries.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ README examples include extremely permissive autoApprove: ['all'], which may cause agents to accept actions without confirmation.
⚠ Sensitive credentials are shown in configuration examples (e.g., DB connection string, API key placeholder); ensure secrets are managed securely.
⚠ Tool schemas, output formats, and error/retry guidance are not documented in the provided README excerpt, so agent behavior may be brittle.

Alternatives

Dedicated services/APIs for text-to-SQL (vendor or internal) with REST/GraphQL interfaces Dify’s official APIs directly for retrieval (without an intermediate MCP wrapper) Other MCP server implementations with richer documentation and standardized tool contracts

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.