Kci Openapi MCP vs KeyCloak MCP

In-depth architectural comparison of the Kci Openapi MCP and KeyCloak MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

K

Choose Kci Openapi MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Kci Openapi MCP Details

Choose KeyCloak MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore KeyCloak MCP Details

Feature & Specification Comparison

Specification	K Kci Openapi MCP Developer Tools	KeyCloak MCP Developer Tools
Summary	KCI (Korea Citation Index) literature & citation search via REST Open API + OAI-PMH	MCP server for KeyCloak Admin REST API via Service Account
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "kci-openapi-mcp": {
      "command": "uvx",
      "args": [
        "--from"
      ]
    }
  }
}

{
  "mcpServers": {
    "keycloak-mcp": {
      "command": "uvx",
      "args": [
        "keycloak-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons