zhineng.dev
English
Get started

MCP collection / by liangshanli

Give AI a next step:
connect real tools.

MCP servers for real development: remote hosts, relational databases, caches and API debugging. Choose what you need and use a compatible client you already know.

5 independent npm packagesStandard MCP connectionsUse independently of this extension
05 TOOLS

SSH

Remote access

@liangshanli/mcp-server-ssh

Run remote commands via SSH and transfer files via SFTP so AI can help investigate and operate within authorized boundaries.

  • Password or private-key authentication, including encrypted keys
  • SHA256 host fingerprint verification
  • Command timeouts, output limits and cancellation
npx -y @liangshanli/mcp-server-ssh
npm documentationConfiguration examples ↗

Node.js 20+. Verify the host fingerprint through a trusted channel before connecting.

MySQL

Databases

@liangshanli/mcp-server-mysql

Give AI MySQL queries, schema management and operation logs, with project-specific permissions and tool prefixes.

  • SELECT / SHOW and DDL / DML operations
  • READONLY mode and granular operation switches
  • Optional TLS, connection pooling and BIGINT strings for precision
npx -y @liangshanli/mcp-server-mysql
npm documentationConfiguration examples ↗

Start with READONLY=true and a read-only database account.

SQL Server

Databases

@liangshanli/mcp-server-mssqlserver

Connect SQL Server with SQL queries, DDL / DML, schema configuration and operation logs for existing business environments.

  • Separate DDL / DROP / DELETE permission switches
  • Schema configuration and connection pooling
  • Database information and operation tracking
npx -y @liangshanli/mcp-server-mssqlserver
npm documentationConfiguration examples ↗

Application switches do not replace database permissions. Use a least-privilege account.

Redis

Data & cache

@liangshanli/mcp-server-redis

Read and manage Redis data and keys through MCP, using permission switches, connection management and logs to investigate issues.

  • Data reads, writes and key management
  • Tools exposed according to permissions
  • Connections, health checks and operation logs
npx -y @liangshanli/mcp-server-redis
npm documentationConfiguration examples ↗

Disable writes first. Production also requires Redis ACLs and network controls.

API Debug

API debugging

@liangshanli/mcp-server-apidebug

Debug APIs in chat, manage base URLs and shared headers, save configurations and execute requests by index.

  • GET / POST / PUT / DELETE / PATCH requests
  • Login requests and shared configuration
  • Saved API lists, indexed execution and help tools
npx -y @liangshanli/mcp-server-apidebug
npm documentationConfiguration examples ↗

Connect only to authorized APIs. Review sensitive data in configuration and logs.

Package details checked on 2026-10-28. See npm for current versions, requirements and capabilities. Copied commands are not executed by this site.

One protocol. Different workflows.

Connect to your tools.
Keep your way of working.

Clients handle connection and authorization; MCP servers supply capabilities. Available tools depend on client versions, configuration and permissions.

01 / SETUP

Choose the client-specific location

Claude Code uses workspace .mcp.json; native VS Code MCP uses .vscode/mcp.json; Cursor uses .cursor/mcp.json.

02 / CONNECT

Validate before connecting

Prepare Node.js, endpoints and a low-privilege account. Test connection and tool discovery before enabling writes or deletes.

03 / USE

Define the task and boundaries

Specify permitted environments and actions. Database permissions, host fingerprints and network policies remain essential; prompts cannot replace them.

Never commit passwords, tokens or private keys to Git. npm launches, remote commands, SQL and API calls can have real effects. Test first.

Build more. Switch less.

Start with one extension, add tools as needed, and try them in a test environment first.

Start your workflow ↗