Aiven + MCP Inspector: Complete MCP Integration

Aiven is a MCP server that Navigate your Aiven projects and interact with the PostgreSQL®, Apache Kafka®, ClickHouse® and OpenSearch® services.

When integrated with MCP Inspector, you can:

• List all projects in your Aiven account
• List all services in a specific project
• Get detailed information about a specific service

This guide provides step-by-step instructions to set up Aiven in MCP Inspector, including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

• Aiven will be fully integrated and operational
• You can use Aiven tools directly in MCP Inspector
• All Aiven capabilities will be available for your workflows
• Access to 5 different tools

Prerequisites

Before starting, ensure you have:

• Aiven API token with appropriate permissions
• MCP Inspector installed and configured
• Compatible operating system (CLI Tool)

Installation

Step 1: Install Aiven

Configuration

Step 2: Configure MCP Inspector

1. Open MCP Inspector settings
2. Navigate to MCP server configuration
3. Add Aiven server with appropriate settings
4. Save and restart if needed

Examples

Once configured, you can use Aiven in MCP Inspector:

Multi-Cloud Database Management

undefined

Ask MCP Inspector: "Check status of all PostgreSQL services and their performance"

Expected Result: undefined

Event Streaming Monitoring

undefined

Ask MCP Inspector: "Show Kafka service health and recent message volumes"

Expected Result: undefined

Analytics Platform Health Check

undefined

Ask MCP Inspector: "Check ClickHouse query performance and storage usage"

Expected Result: undefined

Testing Your Setup

1. Launch MCP Inspector
2. Verify Aiven is available in the tools list
3. Test basic Aiven functionality

Troubleshooting

Common Issues

Connection Failed

Symptoms: Inspector UI shows "Disconnected"

Cause: Server process exited or failed to start.

Solution:

• Check the terminal where you ran npx ... for error output from your server.
• Ensure your server prints JSON-RPC messages to stdout.

Tools Not Showing

Symptoms: Tool list is empty

Cause: Server did not send tools/list response or capabilities negotiation failed.

Solution:

• Check the "Console" or "Logs" tab in the Inspector to see the raw communication.
• Verify your server code correctly implements the ListToolsRequest handler.

Aiven not appearing in MCP Inspector

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check Aiven installation
• Restart MCP Inspector
• Check logs for error messages

Next Steps

Now that Aiven is integrated with MCP Inspector:

• Explore all Aiven capabilities through MCP Inspector
• Check out other MCP servers that work with MCP Inspector
• Join the MCP community for tips and support
• Consider contributing to Aiven development

Need Help?

• Search for Aiven documentation
• Check the MCP Inspector MCP guide
• Join the MCP community discussions