io.github.AceDataCloud/mcp-glm
OfficialRelated Servers
Alternatives to io.github.AceDataCloud/mcp-glm
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceMCP server for OpenAI ChatGPT API. Enables chat completions, vision analysis, embeddings, and model listing through natural language.-
- AlicenseAqualityDmaintenanceMCP server for generating images using Z.AI's glm-image model. Supports image generation with various sizes and qualities, and includes batch CLI functionality.114 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server providing vision understanding tools (image QA, OCR, video and document understanding) via OpenAI-compatible endpoints, defaulting to Zhipu GLM vision models.4MIT

AiChat MCP Serverofficial
AlicenseBqualityBmaintenanceAn MCP server for AI dialogue via the AceDataCloud platform, supporting multi-model conversations including GPT-4/5, DeepSeek, Grok, and GLM.4196 PyPIMIT- AlicenseBqualityDmaintenanceMCP server that provides image analysis, OCR text extraction, and image description using the GLM-4V Flash model from Zhipu AI.38MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for the xAI Grok API, providing tools for chat completions, vision analysis, web/X search, embeddings, and model listing via stdio.-
TDQS
Scored across 3 tools
The three tools serve clearly different purposes: generating a completion, listing models, and reading documentation. The only mild overlap is between the usage-guide tool and the rich descriptions already embedded in the other two tools, which could make an agent ask 'do I need the guide first?'
All tools share a consistent glm_ prefix, and two of three follow a verb_noun pattern (glm_get_usage_guide, glm_list_models). glm_chat_completions breaks the verb-first convention by using a resource path name, but it remains readable and predictable.
Three tools is on the thin side for an API wrapper surface, and one of them (glm_get_usage_guide) is essentially packaged documentation rather than an operational capability. The count is defensible for a narrow single-endpoint wrapper but feels minimal.
Chat completion plus model listing covers the core workflow, but there is no embeddings, no streaming/tokenization, and no non-chat GLM endpoint, so agents needing anything beyond chat hit a dead end. The surface is workable but notably incomplete for a 'GLM API' server.