aerospike

The Aerospike MCP Server provides a controlled interface to interact with an Aerospike cluster through the MCP (Model Context Protocol). It exposes a range of tools for schema discovery, read/write operations, index management, and cluster monitoring, with role-based access control to ensure safety for destructive actions. Typical workflows include inspecting namespaces and sets, retrieving records, and performing batch operations, as well as creating and dropping secondary indexes under admin permissions. You can integrate this MCP server with your IDEs or AI assistants to enable natural-language or structured commands to operate on Aerospike data. The available tools cover schema inspection, query and read operations, write operations, index management, UDF management, and cluster health checks, making it suitable for real-time bidding, ad-tech workloads, and high-throughput data environments.

Prerequisites:

• Go 1.21 or later
• Access to an Aerospike cluster

Installation steps:

1. Clone the repository git clone https://github.com/dringdahl0320/aerospike-mcp-server.git cd aerospike-mcp-server

2. Build from source make build

3. Install (system-wide or location of your choice) make install

4. Prepare configuration Create a configuration file, e.g. aerospike-mcp.json, with your Aerospike connection and permissions settings (see example in the repository README).

5. Run the server with your config aerospike-mcp-server --config /path/to/aerospike-mcp.json

Notes:

• Ensure the Aerospike cluster is reachable from the host running the MCP server.
• Populate the config with appropriate credentials and environment variable references (e.g., AEROSPIKE_PASSWORD) as needed.

Tips and common considerations:

• Role-based access: Use read-only, read-write, and admin roles to control capabilities (e.g., destructive operations require admin).
• Transport options: The MCP server supports stdio, SSE, and websocket transports. Configure transport in your config and IDE integrations as needed.
• Security: If you enable TLS or password-based authentication, ensure environment variables (like AEROSPIKE_PASSWORD) are securely managed.
• Performance: For high-throughput scenarios (Ad-Tech use cases), consider tuning timeout_ms and max_retries in your config and enable appropriate batching for batch operations.
• Debugging: Use the available cluster_info and node_stats tools to monitor health and throughput when troubleshooting performance or connectivity issues.