MCP Demo MCP Server

MCP Demo becomes available to MCP clients through the mcp demo mcp server. 1. Open the Claude Desktop configuration file located at: - On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json - On Windows: %APPDATA%/Claude/claude_desktop_config.json.

What MCP Demo does

1. Open the Claude Desktop configuration file located at: - On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json - On Windows: %APPDATA%/Claude/claude_desktop_config.json

Tools it exposes

Once connected, the assistant can call these 6 tools directly:

• list_projects — List all projects on your Aiven account
• list_services — List all services in a specific Aiven project
• get_service_details — Get the detail of your service in a specific Aiven project
• get_metadata — Get the metadata of a specific Aiven service, currently only working for Aiven for PostgreSQL®
• run_query — Run a query against a specific Aiven service, currently only working for Aiven for PostgreSQL®
• Tools — The Tools tool exposed by this server

Installing the mcp demo mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 3 environment variables: AIVEN_BASE_URL, AIVEN_PROJECT_NAME, AIVEN_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Database servers turn schema archaeology and ad-hoc reporting into conversation, which is why they tend to be the second or third server people install. MCP Demo sits in that group, and the shape of its toolset — list_projects, list_services, get_service_details among others — tells you what it is really for. Worth comparing against the other databases servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by JohnKennedyOSS, written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the mcp demo mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.