home / mcp / dataproc metastore mcp server
MCP Server generated by mcp.ag2.ai
Configuration
View docs{
"mcpServers": {
"ag2-mcp-servers-dataproc-metastore-api": {
"command": "python",
"args": [
"mcp_server/main.py",
"stdio"
],
"env": {
"CONFIG": "<CONFIG>",
"SECURITY": "<SECURITY>",
"CONFIG_PATH": "<CONFIG_PATH>"
}
}
}
}An MCP server provides a stable interface to work with a defined API surface, enabling clients to request and manipulate context-rich model data through the MCP protocol. This server focuses on the Metastore API, exposing its MCP-compatible endpoints so you can integrate with your tooling and workflows without implementing the protocol yourself.
You connect to the MCP server from an MCP client and perform operations through the standard MCP transport. This server runs locally or remotely and exposes a defined set of endpoints that clients can invoke to manage and query context for the Metastore API. Use the client to send requests that create, fetch, update, or delete model-context data as defined by the Metastore MCP surface. The server handles protocol-level details and returns structured responses suitable for your application logic.
Prerequisites you must have before installing and running the MCP server:
git clone <repository-url>
cd mcp_serverpip install -e ".[dev]"
```
Alternatively, you can use UV to install editable dependencies:
```sh
uv pip install --editable ".[dev]"python mcp_server/main.py stdioConfigure the server using environment variables. The following keys are supported for runtime configuration:
Lints and formats the codebase to ensure style and quality across Python files.
Performs static type checking to catch type errors during development.
Runs unit tests and provides test coverage information.
Runs a suite of checks (linting, formatting, security) before each commit.
Used for building and publishing the MCP server package.