GitLab MCP clients reject tools: inputSchema is {} (invalid_literal at inputSchema.type)
Since 2025-11-19, the gitlab-mcp server starts and logs its tool definitions, but no tools load in Cursor, Windsurf, or AMP. Clients fail because each tool's
inputSchemais{}instead of an object withtype: "object"andproperties, producinginvalid_literalerrors attools[0].inputSchema.type. What is the fix?Originally asked on GitHub: https://github.com/zereight/gitlab-mcp/issues/286
5 answers
This is a regression in the gitlab-mcp server: it started reporting tools with an empty
inputSchema, and strict MCP clients reject the whole tool list. A contributor posted PR #285 and said it fixes the issue; after that, users in the thread confirmed tools loaded normally again. No specific release version is named in the thread, so use the build containing PR #285 or apply the patch locally. Note that one later comment from 2025-12-09 says the issue was still present and was reopened as #292, so if it persists after applying the fix, follow that reopened issue.The client-side failure is a schema validation error:
{ "code": "invalid_literal", "expected": "object", "path": ["tools", 0, "inputSchema", "type"], "message": "Invalid literal value, expected \"object\"" }. The fix is on the server side; no client-side config change was identified in the thread.A commenter also linked the problem to a TypeScript SDK issue and suggested pinning
zodto^3.24.2andzod-to-json-schemato^3.23.5in the project dependencies, but the thread does not confirm whether that pin actually resolves it.Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Started gitlab-mcp and inspected the server log; tools were listed with empty
inputSchema, and every client then failed with the schema validation error.Source: https://github.com/zereight/gitlab-mcp/issues/286 (opens external site)
Did this work for you?What @tkruse tried on GitHub (Outcome unclear)
A commenter suggested the empty schema is related to a TypeScript SDK issue and proposed pinning
zodto^3.24.2andzod-to-json-schemato^3.23.5in dependencies.Source: https://github.com/zereight/gitlab-mcp/issues/286#issuecomment-3557349303 (opens external site)
Did this work for you?What @klaudworks tried on GitHub (Outcome unclear)
A contributor linked PR #285 and stated it fixes the problem; the thread does not describe what the PR changes.
Source: https://github.com/zereight/gitlab-mcp/issues/286#issuecomment-3557533752 (opens external site)
Did this work for you?What @feifei325 tried on GitHub (Worked)
After PR #285 was posted, a user reported "It works normally now" and included a screenshot of tools loading in the client.
Source: https://github.com/zereight/gitlab-mcp/issues/286#issuecomment-3557728360 (opens external site)
Did this work for you?
Related questions
- How do I enable pipeline tools in gitlab-mcp (@zereight/mcp-gitlab)?
- How do I configure self-signed certificates or a custom CA for gitlab-mcp?
- GitLab MCP tools skipped: 'missing types in its parameter schema' in Qwen Code / Gemini CLI
- How do I get an MR's milestone in gitlab-mcp when it says 'No milestone assigned'?
- gitlab-mcp 2.1.23 crashes at startup: express-rate-limit does not provide ipKeyGenerator