YDB MCP logo

YDB MCP

by ydb-platform

YDB MCP is a Model Context Protocol server for YDB, enabling interaction with YDB databases from any LLM that supports MCP. This integration facilitates AI-powered database operations and natural language interactions with YDB instances.

View on GitHub

Last updated: N/A

What is YDB MCP?

YDB MCP is a Model Context Protocol server that acts as a bridge between YDB databases and Large Language Models (LLMs). It allows LLMs to interact with YDB databases using natural language, enabling AI-powered database operations.

How to use YDB MCP?

YDB MCP can be used via uvx, pipx, or pip. Configuration involves specifying the YDB endpoint and authentication details (anonymous or login/password) in a JSON format. The configured MCP server can then be used by an MCP client to interact with the YDB database.

Key features of YDB MCP

  • Enables natural language interaction with YDB databases

  • Supports anonymous and login/password authentication

  • Provides tools for running SQL queries, listing directories, and describing paths

  • Integrates with LLMs via the Model Context Protocol

  • Offers a consistent development interface using Make

Use cases of YDB MCP

  • AI-powered data analysis and reporting

  • Natural language querying of YDB databases

  • Automated database management tasks via LLMs

  • Integration of YDB with AI applications

  • Building conversational interfaces for YDB databases

FAQ from YDB MCP

What is MCP?

MCP stands for Model Context Protocol, a standard for communication between LLMs and external tools or services.

What authentication methods are supported?

YDB MCP supports anonymous authentication and login/password authentication.

How do I specify the YDB endpoint?

The YDB endpoint is specified using the --ydb-endpoint argument, e.g., grpc://localhost:2136/local.

What tools are available in YDB MCP?

Available tools include ydb_query, ydb_query_with_params, ydb_list_directory, ydb_describe_path, and ydb_status.

How do I run tests?

Use the make test command. You can control verbosity with the LOG_LEVEL environment variable (e.g., make test LOG_LEVEL=DEBUG).