Antigravity Base MCP Server
Related Servers
Alternatives to Antigravity Base MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA starter template for building MCP servers with TypeScript support, example tools, and automated installation scripts for Claude Desktop, Cursor, and other MCP-compatible AI assistants. Provides a foundation for creating custom tools, resource providers, and prompt templates.8 npm-
- FlicenseCqualityDmaintenanceA starter template for building custom MCP servers with example tools, TypeScript support, and multi-client installation scripts for Claude Desktop, Cursor, and other MCP-compatible AI assistants.28 npm84-
- FlicenseAqualityDmaintenanceA starter template for building custom MCP servers that can integrate with Claude Desktop, Cursor, and other AI assistants. Provides example tools, TypeScript support, and automated publishing workflows to help developers quickly create their own MCP servers.711 npm-
- FlicenseBqualityCmaintenanceA starter template for building custom MCP servers that can integrate with Claude Desktop, Cursor, and other AI assistants. Provides example tools, TypeScript support, and automated publishing workflows to help developers quickly create their own MCP integrations.113 npm-
- FlicenseCqualityDmaintenanceA starter template for building custom MCP servers that can integrate with Claude, Cursor, or other MCP-compatible AI assistants. Provides a clean foundation with TypeScript support, example implementations, and easy installation scripts for quickly creating tools, resources, and prompt templates.212 npm-
- FlicenseAqualityDmaintenanceA starter template for building custom MCP servers with example implementations of tools, resources, and prompts. Includes TypeScript support and installation scripts for Claude Desktop, Cursor, and other MCP-compatible clients.29 npm-
TDQS
Scored across 3 tools
echo and get_system_info are clearly distinct operations, and my_custom_tool is not described in a way that directly overlaps with them. However, the placeholder description for my_custom_tool leaves its actual purpose ambiguous, so the set is not perfectly unambiguous.
The naming is inconsistent: echo uses a bare verb, get_system_info follows verb_noun, and my_custom_tool uses a vague custom label. There is no shared naming convention across the three tools.
Three tools is not an unreasonable number by itself, but the set feels like a minimal scaffold rather than a focused server. The unrelated utilities and placeholder custom tool make the count less defensible than it would be with a clear shared purpose.
The server lacks a coherent domain, so it is difficult to determine what complete coverage would look like. echo and get_system_info are isolated utilities, while my_custom_tool is an unspecified placeholder, leaving obvious gaps in any implied workflow.