Antigravity Base MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_LOG_LEVEL | No | Logging level for the MCP server (e.g. 'info'). This is used in client configuration examples. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoA | Echoes back the input message with optional repetition and prefix formatting. |
| get_system_infoA | Retrieves current system diagnostics including OS, Node version, memory, and CPU info. |
| my_custom_toolD | Detailed description of what this tool accomplishes, its expected input, and its output format. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_code_snippet | Generates a structured prompt to perform deep code analysis, security audit, and refactoring |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Server Status & Health | Current runtime configuration and server health status |
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.