Skip to main content

godot-mcp vs Glama

godot-mcpGlama

Bottom line: godot-mcp for godot developers using Claude Code; Glama for developers evaluating MCP servers.

MCP server that lets an agent run your Godot game and read back the errors

Visit

MCP server registry, in-browser inspector, and gateway with an LLM API bundled in.

Visit
Votes00
PricingFreeFreemium
CategoryMcpMcp
Tags
godotmcpclaude codegame developmentopen source
mcpregistrygatewayllm-apiinspector
Best for
  • Godot developers using Claude Code
  • agent run-and-debug loops
  • scene and node editing from prompts
  • Developers evaluating MCP servers
  • Teams wanting gateway governance
  • Open-source server authors seeking free hosting
Pros
  • Free and MIT-licensed
  • Clean run-and-read-error loop
  • No GPU required
  • Simple Claude Code setup
  • Very large indexed server catalog
  • In-browser MCP Inspector for safe testing
  • Gateway adds logging, access control, and managed OAuth
  • Bundled unified LLM API across major providers
  • Free hosting for open-source servers
Cons
  • Community project, no official support
  • Active open issue/PR backlog
  • Godot-only
  • Self-reported scale is hard to independently verify
  • Per-server-instance pricing may surprise some users
  • Hosted-only platform, no self-hosting of Glama itself
  • Crowded, fast-changing registry landscape
  • Third-party server trust remains the user's responsibility

Comparison generated from each tool's listing. Add or remove tools above to change it.