M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionIBM i MCP ServerMCP server for IBM i systems, providing secure SQL-based access.MCP ClickHouseConnect ClickHouse to your AI assistants
FMRS42 / 100 · D79 / 100 · B
Reliability5 / 2012 / 20
Security and permissions6 / 2018 / 20
Maintenance7 / 2017 / 20
Documentation13 / 2017 / 20
Setup experience11 / 2015 / 20
Best for
  • Building AI agents or AI-powered applications that interact with IBM i.
  • Requiring remote server support over the MCP protocol (stdio or HTTP).
  • Leveraging Mapepire for fast, lightweight, low-latency database access.
  • Defining custom SQL tools via YAML.
  • Teams already using ClickHouse who want AI assistants to access data directly.
  • Scenarios requiring fast, read-only data queries and schema exploration.
Not for
  • Terminal-first interactions without an MCP client; the `ibmi` CLI is better for that.
  • IBM i systems without Mapepire installed.
  • Scenarios requiring traditional ODBC/JDBC database access.
  • Simple SQL query tools without AI or MCP integration.
  • Scenarios requiring write access to the database without explicit opt-in.
  • Production environments with stringent security requirements that avoid default permission settings.
Required permissions
  • Requires IBM i credentials (username and password) for database access.
  • Requires Mapepire server running on IBM i (default port 8076).
  • May require network access to the specified port on the IBM i system.
  • Needs access to QSYS2 system views and tables for the example tools.
  • Requires read-only access to ClickHouse database (default).
  • Optional: write access via CLICKHOUSE_ALLOW_WRITE_ACCESS.
  • Optional: destructive operations via CLICKHOUSE_ALLOW_DROP.
Risks and side effects
  • Credential management: passing passwords directly can be risky; use environment variables or secure storage.
  • Network attack surface: exposing the MCP server over HTTP could allow unauthorized access unless secured (HTTPS, authentication).
  • Data exposure: SQL tools may access sensitive data; restrict tool scope.
  • Resource consumption: long-running queries may impact IBM i performance.
  • If write access is enabled, AI might make unintended modifications.
  • If DROP access is enabled, data deletion could occur accidentally.
  • Credentials may be exposed via environment variables.
Supported clientsClaude Desktop, VSCode Copilot, BobClaude Desktop
Tools14