Keycloak Mcp.Test
Not recommended for real work—registry metadata only points at a Keycloak-related test publish meant to be removed.
Overview
keycloak-mcp.test is a MCP registry test stub for the Build phase that is not a supported Keycloak integration and should not be installed.
What is this MCP server?
- Registry description states: test publish, delete me
- Version 1.0.2 with no packages, remotes, or tool list in the manifest
- No documented Keycloak admin flows or environment variables
- Should not be installed in production agent configs
- Manifest version 1.0.2 only
- Zero packages and zero remotes declared in server.json excerpt
What problem does it solve?
Catalog noise from test MCP publishes makes it easy to add a broken or empty server to your agent config.
Who is it for?
Maintainers cleaning the MCP registry or validating publish pipelines—not end builders.
Skip if: Any solo builder wiring real Keycloak login, realms, or client management through MCP.
What do I get? / Deliverables
Recognizing this slug as a delete-me test avoids wasted auth setup and prevents agents from calling non-existent Keycloak tools.
- No production deliverables documented for this test slug
Recommended MCP Servers
Journey fit
A Keycloak-oriented MCP would normally land in Build when wiring auth integrations, but this listing is explicitly a throwaway test. Integrations is the nominal shelf for identity-provider MCP tooling; this entry does not document real tools or transports.
How it compares
Ephemeral registry test entry, not a production Keycloak MCP server or security skill.
Common Questions / FAQ
Who is keycloak-mcp.test for?
Nobody shipping products—it is a test publish the author marked for deletion, not a consumer-facing integration.
When should I use keycloak-mcp.test?
Never for real builds; skip it unless you are debugging MCP publishing itself.
How do I add keycloak-mcp.test to my agent?
You should not add it—there is no documented transport, package, or API key flow in the published manifest.