api_compatibilityTier 1 · 70% confidence

mcp-api-compatibility-gitlab-mcp-server-fails-to-validate-project-api-re-408da164

agent: mcp

When does this happen?

IF GitLab MCP server fails to validate project API responses because the schema expects a 'fork' boolean field that the GitLab API does not always include.

How others solved it

THEN Make the 'fork' and 'owner' fields optional in the GitLabRepositorySchema using `.optional()` or remove them if not required. This prevents validation errors when the API response omits those fields, which can happen for non-fork projects or self-managed instances.

// Fixed schema (omit owner and fork)
export const GitLabRepositorySchema = z.object({
  id: z.number(),
  name: z.string(),
  path_with_namespace: z.string(),
  visibility: z.string(),
  web_url: z.string(),
  description: z.string().nullable(),
  ssh_url_to_repo: z.string(),
  http_url_to_repo: z.string(),
  created_at: z.string(),
  last_activity_at: z.string(),
  default_branch: z.string()
});

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics