agent-builder-mcp

Generate MCP JSON configs for Elastic Agent Builder tools.

6|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/patrykkopycinski/elastic-cursor-plugin --skill agent-builder-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-builder-mcp
Source: https://github.com/patrykkopycinski/elastic-cursor-plugin/tree/main/.cursor/skills/agent-builder-mcp
Command: npx skills add https://github.com/patrykkopycinski/elastic-cursor-plugin --skill agent-builder-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Elastic Agent Builder workflows and organization-specific tools are difficult to create, validate, and expose to IDEs without a simple, repeatable process; this Skill bridges the gap by guiding tool definition, testing, listing, and MCP configuration for Cursor/Claude integration.

Core Features & Use Cases

  • Tool Definition: Help define new Agent Builder tools with name, description, and optional input schema so they can be created via the UI or API.
  • Discovery & Testing: List existing Agent Builder tools and run test invocations to validate behavior before production use.
  • MCP Integration: Produce and explain the MCP JSON config (including transport) required to connect Cursor or Claude to an Agent Builder MCP endpoint.
  • Use Case: A developer wants to add an organization-specific search tool from Agent Builder into Cursor; use this Skill to define the tool, test it locally, and generate the MCP config to enable it in the IDE.

Quick Start

Use this Skill to list Agent Builder tools and generate the MCP JSON you can paste into Cursor MCP settings to make those tools available in your IDE.

Frequently Asked Questions about agent-builder-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect Elastic Agent Builder tools to Cursor?

To connect Elastic Agent Builder tools to Cursor, you generate an MCP JSON configuration using your Agent Builder endpoint and paste it into your Cursor MCP settings. This configuration includes the URL and transport needed to expose your custom tools directly within the IDE.

What is an MCP configuration for connecting Claude or Cursor to custom tools?

An MCP configuration is a JSON snippet that links an IDE like Cursor or Claude to an external tool endpoint. It specifies the URL and transport protocol, allowing the IDE to invoke custom Agent Builder tools during development workflows.

How do I test custom tools before adding them to my IDE?

You test custom tools by listing existing Agent Builder tools and running test invocations against your endpoint. This validates the tool's behavior and ensures it functions correctly before you move to production or generate the MCP configuration.

Do I need a Kibana endpoint to define and manage Agent Builder tools?

Yes, you need access to an Agent Builder endpoint, such as Kibana or an organization API, to define, list, and test custom tools. This endpoint serves as the backend for managing tools and generating the required MCP configuration.

What's the best way to define an Agent Builder tool with an input schema?

The best way to define an Agent Builder tool is to specify its name, description, and optional input schema via the UI or API. Once created through the Agent Builder endpoint, the tool can be tested locally before generating the MCP JSON for IDE integration.