How to integrate Kibana MCP with Claude Agent SDK

This guide walks you through connecting Kibana to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Kibana agent that can visualize weekly sales data as a chart, list top error logs from last 24 hours, generate dashboard of user activity trends through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Kibana account through Composio's Kibana MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Kibana logoKibana
Api KeyBasic

Kibana is a visualization and analytics platform for Elasticsearch data. It helps you explore, visualize, and monitor your data using intuitive dashboards and interactive tools.

47 Tools

Introduction

This guide walks you through connecting Kibana to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Kibana agent that can visualize weekly sales data as a chart, list top error logs from last 24 hours, generate dashboard of user activity trends through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Kibana account through Composio's Kibana MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Kibana with

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Kibana
  • Configure an AI agent that can use Kibana as a tool
  • Run a live chat session where you can ask the agent to perform Kibana operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK 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

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Kibana account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Kibana functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Kibana
  const session = await composio.create(USER_ID, {
    toolkits: ['kibana'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Kibana
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Kibana tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Kibana
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

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

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['kibana']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Kibana tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Kibana through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

Every Kibana action and event your agent gets out of the box.

Delete Alerting Rule

Tool to delete an alerting rule in Kibana.

Delete Connector

Tool to delete a connector in Kibana.

Delete Fleet Output

Tool to delete a specific output configuration in Kibana Fleet.

Delete Fleet Proxy

Deletes a Fleet proxy configuration by its unique identifier.

Delete List

Deletes a list.

Delete Osquery Saved Query

Delete a saved Osquery query by its saved object ID.

Delete Saved Object

Tool to delete a saved object in Kibana.

Find Kibana Alerts

Tool to find and/or aggregate detection alerts in Kibana.

Get Action Types

Retrieves all available connector types (actions) in Kibana.

Get Alerting Rules

Tool to retrieve a list of alerting rules in Kibana.

Get Rule Types

Retrieves available rule types (alert types) in Kibana.

Get Cases

Tool to retrieve a list of cases in Kibana.

Get All Connectors

Tool to retrieve a list of all connectors in Kibana.

Get Data Views

Retrieves all data views (formerly known as index patterns) available in Kibana.

Find Detection Engine Rules

Retrieves a paginated list of Kibana detection engine rules with flexible filtering and sorting options.

Get Endpoint List Items

Retrieves Elastic Endpoint exception list items with filtering, pagination, and sorting capabilities.

Get Entity Store Engines

Retrieves all entity store engines configured in Kibana.

List Entity Store Entities

Tool to list entity records in the entity store with support for paging, sorting, and filtering.

Get Entity Store Status

Retrieves the current status of the Kibana Entity Store and its configured engines.

Get Fleet Agent Policies

Retrieves a paginated list of Fleet agent policies with filtering, sorting, and optional detailed information.

Get Fleet Agents Available Versions

Tool to retrieve the available versions for Fleet agents.

Get Fleet Agents Setup Status

Check Fleet setup readiness and identify missing requirements.

Check Fleet Permissions

Tool to check the permissions for the Fleet API.

Get Fleet Enrollment API Key

Tool to retrieve details of a specific enrollment API key by its ID.

Get Fleet Enrollment API Keys

Tool to fetch a list of enrollment API keys.

Get Fleet EPM Categories

Get all available package categories in the Elastic Package Manager (EPM) with package counts.

Get Fleet EPM Data Streams

Tool to retrieve the list of data streams in the Elastic Package Manager.

Get Fleet EPM Package Details

Retrieves comprehensive details for a specific Fleet integration package version from the Elastic Package Manager (EPM).

Get Fleet EPM Package File

Retrieves a specific file from an Elastic Package Manager (EPM) package.

Get Fleet EPM Packages

Tool to fetch the list of available packages in the Elastic Package Manager.

Get Installed EPM Packages

Tool to retrieve the list of installed packages in the Elastic Package Manager.

Get Fleet EPM Packages (Limited)

Retrieves a limited list of package names from the Elastic Package Manager (EPM) registry.

Get EPM Package Statistics

Retrieves usage statistics for a specific Fleet package in Kibana, including the number of package policies and agent policies using the package.

Get Fleet Package Policies

Retrieves a list of Fleet package policies (integration policies) in Kibana.

Get Fleet Server Host

Tool to fetch details of a specific Fleet server host by its item ID.

Get Fleet Server Hosts

Tool to retrieve the list of Fleet Server hosts.

Get Index Management Indices

Tool to fetch information about indices managed by Kibana's Index Management feature.

Get Node Metrics

Tool to retrieve statistics for nodes in an Elasticsearch cluster, often visualized in Kibana.

Get Reporting Jobs

Tool to retrieve a list of reporting jobs in Kibana.

Get Saved Objects

Tool to retrieve a list of saved objects in Kibana based on specified criteria.

Get Kibana Status

Tool to get the current status of Kibana.

Create Alerting Rule

Tool to create a new alerting rule in Kibana.

Create Case

Tool to create a new case in Kibana.

Create Kibana Connector

Tool to create a new connector in Kibana.

Create Dashboard

Tool to create a new dashboard in Kibana.

Create Data View

Tool to create a new data view (index pattern) in Kibana.

Create or Update Saved Object

Tool to create or update a saved object in Kibana.

FAQ

Frequently asked questions

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.

Yes, you can. Claude Agent SDK 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.

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.

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.

Start with Kibana.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Kibana tool your agent needs.Free to start.

Start building