-
Notifications
You must be signed in to change notification settings - Fork 0
Revise README for ScalarDB MCP Server details #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,55 @@ | ||
| # Standard repository template | ||
| # ScalarDB MCP Server | ||
|
|
||
| The purpose of this repository template is to streamline the creation of commonly used files when we create new repositories. | ||
| ScalarDB MCP Server is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) implementation that enables LLMs to access and manage your data through ScalarDB. By leveraging LLMs, you can use natural language to search and update across multiple, potentially siloed, databases. | ||
|
|
||
| ## What is ScalarDB MCP Server? | ||
|
|
||
| ScalarDB MCP Server works seamlessly whether you're using a single database or multiple databases. Unlike traditional approaches that require separate MCP servers for each database, ScalarDB MCP Server leverages the [multi-storage capabilities of ScalarDB](https://scalardb.scalar-labs.com/docs/latest/multi-storage-transactions) to provide unified access to heterogeneous databases (PostgreSQL, MySQL, Cosmos DB, DynamoDB, etc.) through a single MCP server. By simply submitting queries in natural language, the server automatically executes the appropriate operations across your databases, improving and accelerating decision-making processes. | ||
|
|
||
| <img src="docs/images/architecture.png" alt="ScalarDB MCP Server Architecture" width="400"> | ||
|
|
||
| ### Key features | ||
|
|
||
| - **Works with single or multiple databases:** Whether you have one database or many databases managed by ScalarDB, ScalarDB MCP Server provides a unified natural language interface. | ||
| - **AI-powered automation:** Use conversational queries—the LLM automatically generates and executes the appropriate database operations. | ||
| - **ACID-compliant transactions:** Maintain data integrity with full transactional support across databases. | ||
| - **Dual operational modes:** SQL mode for ScalarDB Cluster (leveraging the SQL interface) or CRUD mode for ScalarDB Community edition (by using ScalarDB Core). | ||
|
|
||
| ## Docs | ||
|
|
||
| * **[Getting Started with ScalarDB MCP Server](https://scalardb.scalar-labs.com/docs/latest/scalardb-mcp-server/getting-started):** Installation and quickstart guide | ||
| * **[ScalarDB MCP Server Tools Reference](https://scalardb.scalar-labs.com/docs/latest/scalardb-mcp-server/tools-reference):** Complete documentation of all available MCP tools | ||
|
|
||
| ## Quickstart | ||
|
|
||
| Get started with ScalarDB MCP Server in three steps: | ||
|
|
||
| 1. **Install:** Download the Docker image or JAR file. | ||
| 2. **Configure:** Connect to your ScalarDB deployment and MCP client. | ||
| 3. **Use:** Start querying your databases by using natural language. | ||
|
|
||
| For complete installation and setup instructions, see [Getting Started with ScalarDB MCP Server](https://scalardb.scalar-labs.com/docs/latest/scalardb-mcp-server/getting-started). | ||
|
|
||
| **Example queries once configured:** | ||
|
|
||
| - `Show me all users from the customer table` | ||
| - `Create a new table called products with columns id, name, and price` | ||
| - `Get user profile and order history for user ID 123` | ||
|
|
||
| ## ScalarDB version compatibility | ||
|
|
||
| | ScalarDB MCP Server | ScalarDB Community | ScalarDB Cluster | Java Version | | ||
| |---------------------|--------------------|------------------|--------------| | ||
| | 0.9.x | 3.16+ | 3.16+ | 17+ | | ||
|
|
||
| **Note about operational mode:** | ||
| - **ScalarDB Cluster:** Use SQL mode for efficient operations (recommended) or CRUD mode for granular control. | ||
| - **ScalarDB Community edition:** Use CRUD mode only (SQL interface not available). | ||
|
|
||
| ### Reporting issues | ||
|
|
||
| If you find a bug or have a feature request, please [open an issue](https://github.com/scalar-labs/scalardb-mcp-server/issues). | ||
|
|
||
| ## Community | ||
|
|
||
| - **[ScalarDB Documentation](https://scalardb.scalar-labs.com/):** Learn more about ScalarDB. | ||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.