How to integrate Kibana MCP with Claude Code

Framework Integration Gradient
Kibana Logo
Claude Code Logo
divider

Introduction

Manage your Kibana directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Rube - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Why Rube?

Rube is a universal MCP server with access to 850+ SaaS apps. It ensures just-in-time tool loading so Claude can access the tools it needs, a remote workbench for programmatic tool calling and handling large tool responses out of the LLM context window, ensuring the LLM context window remains clean.

Connect Kibana to Claude Code with Rube

1. Get the MCP URL

Copy and paste the below command in Claude Code to add Rube MCP.

Terminal

2. Authenticate Rube

Run /mcp to view Rube

bash
/mcp
Run /mcp to view Rube in Claude Code
Click on Rube to authenticate
Authentication flow complete

3. Ensure it's connected

Run /mcp again to verify the connection. Now, do whatever you want with Claude Code and Kibana.

Rube connected successfully

Supported Tools & Triggers

Tools
Delete ActionTool to delete an action in kibana.
Delete Alerting RuleTool to delete an alerting rule in kibana.
Delete ConnectorTool to delete a connector in kibana.
Delete Fleet OutputTool to delete a specific output configuration in kibana fleet.
Delete Fleet ProxyTool to delete a specific fleet proxy configuration by its id.
Delete ListDeletes a list.
Delete Osquery Saved QueryTool to delete a saved osquery query by its id.
Delete Saved ObjectTool to delete a saved object in kibana.
Find Kibana AlertsTool to find and/or aggregate detection alerts in kibana.
Get Action TypesTool to fetch the list of available action types (e.
Get Alerting RulesTool to retrieve a list of alerting rules in kibana.
Get Alert TypesTool to retrieve available alert types in kibana.
Get CasesTool to retrieve a list of cases in kibana.
Get All ConnectorsTool to retrieve a list of all connectors in kibana.
Get Data ViewsTool to retrieve a list of data views available in kibana.
Find Detection Engine RulesRetrieves a list of detection engine rules based on specified criteria.
Get Endpoint List ItemsTool to retrieve all items from an endpoint exception list.
Get Entity Store EnginesRetrieves the list of engines from the entity store.
List Entity Store EntitiesTool to list entity records in the entity store with support for paging, sorting, and filtering.
Get Entity Store StatusTool to retrieve the status of the entity store in kibana.
Get Fleet Agent PoliciesFetches a list of agent policies in fleet.
Get Fleet Agents Available VersionsTool to retrieve the available versions for fleet agents.
Get Fleet Agents Setup StatusTool to check if the fleet agents are set up.
Check Fleet PermissionsTool to check the permissions for the fleet api.
Get Fleet Data StreamsRetrieves the list of data streams in fleet.
Get Fleet Enrollment API KeyTool to retrieve details of a specific enrollment api key by its id.
Get Fleet Enrollment API KeysTool to fetch a list of enrollment api keys.
Get Fleet EPM CategoriesTool to fetch the list of categories in the elastic package manager.
Get Fleet EPM Data StreamsTool to retrieve the list of data streams in the elastic package manager.
Get Fleet EPM Package DetailsTool to fetch details of a specific package and version in the elastic package manager (epm).
Get Fleet EPM Package FileTool to retrieve a specific file from a package in the elastic package manager.
Get Fleet EPM PackagesTool to fetch the list of available packages in the elastic package manager.
Get Installed EPM PackagesTool to retrieve the list of installed packages in the elastic package manager.
Get Fleet EPM Packages (Limited)Tool to fetch a limited list of packages from the elastic package manager.
Get EPM Package StatisticsTool to retrieve statistics for a specific package in the elastic package manager.
Get Fleet Package PoliciesTool to retrieve a list of all package policies (agent & epm), providing their ids and associated details.
Get Fleet Server HostTool to fetch details of a specific fleet server host by its item id.
Get Fleet Server HostsTool to retrieve the list of fleet server hosts.
Get Index Management IndicesTool to fetch information about indices managed by kibana's index management feature.
Get Node MetricsTool to retrieve statistics for nodes in an elasticsearch cluster, often visualized in kibana.
Get Reporting JobsTool to retrieve a list of reporting jobs in kibana.
Get Saved ObjectsTool to retrieve a list of saved objects in kibana based on specified criteria.
Get Kibana StatusTool to get the current status of kibana.
Create Alerting RuleTool to create a new alerting rule in kibana.
Create CaseTool to create a new case in kibana.
Create Kibana ConnectorTool to create a new connector in kibana.
Create DashboardTool to create a new dashboard in kibana.
Create Data ViewTool to create a new data view (index pattern) in kibana.
Create or Update Saved ObjectTool to create or update a saved object in kibana.

What is the Kibana MCP server, and what's possible with it?

The Kibana MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Kibana account. It provides structured and secure access so your agent can perform Kibana operations on your behalf.

Connecting Kibana via Tool Router

Tool Router is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Kibana) for even more tool search precision. It's secure and reliable.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Kibana account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["kibana"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http kibana-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Kibana. This URL will be used to connect Claude Code to Kibana.

What's happening:

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Kibana
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Kibana MCP to Claude Code

bash
claude mcp add --transport http kibana-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (kibana-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Kibana MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your kibana-composio entry in the list
  • This confirms that Claude Code can now access Kibana tools

If everything is wired up, you should see your kibana-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Kibana

The first time you try to use Kibana tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Kibana
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Kibana authorization flow
  • Return to the terminal and start using Kibana through Claude Code

Once authenticated, you can ask Claude Code to perform Kibana operations in natural language. For example:

  • "Visualize weekly sales data as a chart"
  • "List top error logs from last 24 hours"
  • "Generate dashboard of user activity trends"

Complete Code

Here's the complete code to get you started with Kibana and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["kibana"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http kibana-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Kibana with Claude Code using Composio's MCP server. Now you can interact with Kibana directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Kibana operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Kibana operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build Kibana MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Kibana MCP?

With a standalone Kibana MCP server, the agents and LLMs can only access a fixed set of Kibana tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Kibana and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Kibana tools.

Can I manage the permissions and scopes for Kibana while using Tool Router?

Yes, absolutely. You can configure which Kibana scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Kibana data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.