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.DBHubBytebase's official, minimalist two-tool database MCP server
FMRS42 / 100 · D74 / 100 · B
Reliability5 / 2013 / 20
Security and permissions6 / 2013 / 20
Maintenance7 / 2016 / 20
Documentation13 / 2015 / 20
Setup experience11 / 2017 / 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.
  • Scenarios wanting the smallest possible tool count and lowest context-window overhead for database access
  • Cases needing to grant non-technical teammates safe, read-only database access
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 needing database administration operations (creating indexes, altering schema) rather than just querying (DBHub is positioned as a query tool, not a DBA management tool)
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 a database connection string (DSN), which may contain sensitive credentials
  • execute_sql can run arbitrary SQL (including writes) by default — must be constrained via read-only mode or the underlying database account's own permissions
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.
  • Under default settings, if the connected database account has write access, execute_sql could let the assistant perform an unintended write or delete — pair with a read-only database account in production
  • The DSN contains a plaintext password — pay attention to the access permissions on wherever the config is stored
Supported clientsClaude Desktop, VSCode Copilot, BobClaude Desktop, Claude Code, VS Code, Cursor, Zed
Tools12