MCP server

Aerospike Voyager includes an embedded Model Context Protocol (MCP) server that lets AI coding agents interact directly with your Aerospike clusters. Instead of guessing at schema or pasting documentation into chat, your AI agent can inspect and query the actual data.

What can AI agents do through the MCP server?

When connected to Voyager’s MCP server, an AI coding agent can:

Browse cluster structure: list namespaces, sets, and nodes.
Query and filter records: read records by key, run queries with filter expressions, and check record existence.
Create, update, and delete records: write new records, update bins, delete records, and truncate sets.
Manage connections: create, test, and switch between cluster connections.
Run info commands: issue Aerospike info protocol commands against the cluster or a specific node.

For the full list of available tools, see the Tool reference.

Access profiles

Voyager provides two access profiles that control which tools are available to your AI coding agent:

All tools enabled (default): All tools are available. The agent can read, write, delete, manage connections, and run info commands.
Browse and read only: Browse and read operations only. Write, delete, and info commands are blocked at call time. execute_info and execute_info_on_node are blocked because the Aerospike info protocol supports mutation subcommands. Use this for safe exploration.

Switch profiles on the MCP Server page in Voyager.

Transport

The MCP server uses Streamable HTTP on localhost:9090 by default. Both the port and bind interface are configurable from the MCP Server page in Voyager. The server does not start automatically with Voyager — toggle it on from the MCP Server page before connecting an agent. See Setup.

Authentication

Token-based authentication is optional but recommended. When enabled, your AI coding agent must include a Bearer token in the Authorization header. See Setup for configuration details.

Supported AI coding agents

Voyager works with any MCP-compatible agent. The MCP Server page in Voyager provides ready-to-copy setup snippets for:

Claude Code
OpenAI Codex CLI
Google Gemini CLI

Any editor or agent that supports the MCP Streamable HTTP transport (Cursor, VS Code, Claude Desktop, Windsurf, Zed) can also connect using the JSON configuration block shown on the MCP Server page.