1. Conduid
  2. Developer Tools
  3. Dev Tools MCP Server
MCP server · Developer Tools

Dev Tools MCP Server

MCP server: Dev Tools MCP Server

Unclaimed last commit 6 months ago devtools
47Fair

Scored 4 months ago · breakdown

About Dev Tools MCP Server

Dev Tools MCP Server is an MCP server published by mono-harold in the Developer Tools category: mCP server: Dev Tools MCP Server. It has been installed 0 times through Conduid.

Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx dev-tools-mcp-server

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Dev Tools MCP Server

Powered by Claude · Grounded in docs

I know everything about Dev Tools MCP Server. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

MCD MCP Server

An MCP (Model Context Protocol) server that connects Claude AI to the MCD PaaS API. It allows Claude to query database table definitions from the Monoplus Cloud (Sinfonia Cloud) platform through natural language.

What it does

This server acts as a bridge between Claude Desktop and the MCD PaaS REST API. When Claude needs information about database tables — their structure, metadata, creation dates, or categories — it calls this server, which handles authentication and API communication behind the scenes.

Currently available tools:

  • get_db_table_definition — Search for database table definitions by category name and/or table name.

Prerequisites

  • Python 3.12+
  • uv package manager
  • Access to an MCD PaaS API instance
  • Claude Desktop (for MCP integration)

Setup

  1. Install dependencies:

    uv sync
    
  2. Copy .env.sample to .env and fill in your credentials:

    cp .env.sample .env
    

    Required variables:

    Variable Description
    MCD_PAAS_API_BASE Base URL of the MCD PaaS API
    LOGIN_COMPANY_CD Company code for authentication
    LOGIN_USER_ID User ID
    LOGIN_PASSWORD Password
    LOGIN_BRANCH_NAME Branch name (e.g., develop)
  3. Configure Claude Desktop by adding the server to claude_desktop_config.json (see config/claude_desktop_config.json for a reference). If running from WSL, make sure to use the correct distribution name and set "WSL_UTF8": "1" in the env block.

Running

# Via the wrapper script (used by Claude Desktop)
./run-mcp.sh

# Or directly
uv run python main.py

The server communicates over stdio using the MCP protocol. Debug logs are written to /tmp/mcp-debug.log.

README mirrored from the source repository 4 months ago. The original is authoritative.

Questions

About Dev Tools MCP Server

How do I install Dev Tools MCP Server?

Run npx dev-tools-mcp-server, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Dev Tools MCP Server safe to use with an AI agent?

Its trust score is 47 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Dev Tools MCP Server still maintained?

The last commit was 6 months ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.