FANNG1 commented on code in PR #7905: URL: https://github.com/apache/gravitino/pull/7905#discussion_r2256491238
########## mcp-server/README.md: ########## @@ -0,0 +1,63 @@ +<!-- + Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. +--> + +Gravitino MCP server provides the ability to manage Gravitino metadata for LLM. + +### Requirement: + +1. Python 3.10+ +2. uv is installed. You can install uv by following the [official guide](https://docs.astral.sh/uv/getting-started/installation/). + +### How to run: + +1. Clone the code from GitHub, and change to `mcp-server` directory +2. Create virtual environment, `uv venv` +3. Install the required Python packages. `uv pip install -e .` +4. Add Gravitino MCP server to corresponding LLM tools, use local MCP server like: Review Comment: Different LLM tools may have different ways to add MCP server configuration, but they all use the same mcp server configurations as my test for cursor, claud, trae. Adding such detailed steps for diverse LLMs is not a good way and hard to maintance, may be we could use one LLM tools as example, WDYT? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
