Skip to main content
Glama

HelpAddToClient

Add the RushDB MCP server to your client to access a zero-config graph database for builders, AI agents, and SaaS teams.

Instructions

Help the user add the RushDB MCP server to their MCP client

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that returns static instructions on how to install and configure the RushDB MCP server in an MCP client.
    export async function HelpAddToClient() {
      return {
        instructions: `To add the RushDB MCP server to your MCP client, follow these steps:
    
    1. **Install the RushDB MCP Server**:
       \`\`\`bash
       npm install -g @rushdb/mcp-server
       \`\`\`
    
    2. **Get your RushDB API Key**:
       - Visit https://rushdb.com
       - Sign up for an account or log in
       - Navigate to your API settings to get your API key
    
    3. **Configure your MCP client**:
       Add the following to your MCP client configuration:
    
       **For Claude Desktop** (~/Library/Application Support/Claude/claude_desktop_config.json):
       \`\`\`json
       {
         "mcpServers": {
           "rushdb": {
             "command": "npx",
             "args": ["@rushdb/mcp-server"],
             "env": {
               "RUSHDB_API_KEY": "your-rushdb-api-key-here"
             }
           }
         }
       }
       \`\`\`
    
       **For other MCP clients**, check their documentation for how to add MCP servers.
    
    4. **Restart your MCP client** to load the RushDB server.
    
    5. **Test the connection** by asking your client to list the available RushDB tools.
    
    **Available Environment Variables**:
    - \`RUSHDB_API_KEY\`: Your RushDB API key (required)
    
    **What you can do with RushDB MCP Server**:
    - Create, read, update, and delete records
    - Search across records using RushDB's powerful query language
    - Manage relationships between records
    - Export data to CSV
    - Browse labels and properties in your database
    - Work with RushDB's Labeled Meta Property Graph (LMPG) architecture
    
    For more information, visit https://docs.rushdb.com`
      }
    }
  • The tool schema definition including name, description, and empty input schema (no parameters required).
    {
      name: 'HelpAddToClient',
      description: 'Help the user add the RushDB MCP server to their MCP client',
      inputSchema: { type: 'object', properties: {}, required: [] }
    },
  • index.ts:331-340 (registration)
    The switch case in the CallToolRequestSchema handler that registers and dispatches calls to the HelpAddToClient tool function.
    case 'HelpAddToClient':
      const helpAddToClientResult = await HelpAddToClient()
      return {
        content: [
          {
            type: 'text',
            text: helpAddToClientResult.instructions
          }
        ]
      }
  • index.ts:72-76 (registration)
    The request handler for listing tools, which includes HelpAddToClient via the imported 'tools' array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools
      }
    })
  • index.ts:39-39 (registration)
    Import statement for the HelpAddToClient handler function.
    import { HelpAddToClient } from './tools/HelpAddToClient.js'
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states what the tool does but lacks behavioral details such as whether it modifies system files, requires user permissions, provides interactive prompts, or handles errors. For a configuration tool with zero annotation coverage, this is a significant gap in disclosing operational traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no wasted words. It is front-loaded with the core purpose and efficiently communicates the tool's function without redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a configuration action with no parameters) and lack of annotations or output schema, the description is minimal but adequate. It states the purpose clearly but does not provide details on behavior, outcomes, or error handling, which could be beneficial for such a tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details, which is appropriate. Baseline is 4 for zero parameters, as it avoids unnecessary information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Help the user add') and the target resource ('the RushDB MCP server to their MCP client'). It distinguishes itself from all sibling tools, which are focused on database operations like CreateRecord, FindRecords, etc., making this a unique configuration/installation tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (when setting up or configuring the MCP client with RushDB), but it does not explicitly state when to use this tool versus alternatives or provide exclusions. It's clear from the purpose that this is for initial setup, but no specific guidance on prerequisites or timing is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rush-db/RushDB'

If you have feedback or need assistance with the MCP directory API, please join our Discord server