# Reported issues for greptimedb-mcp-server

Pod holds 11 of 11 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [greptimedb-mcp-server](/mcp/greptimedb-mcp-server).

## Most discussed

### Feature request: Support always-on / HTTP-based MCP server mode for long-running usage

## Summary / Motivation
Currently, greptimedb-mcp-server runs using a transport (stdio / FastMCP default) that expects a client to attach. As a result — when no client connects (e.g. in container / Kubernetes environment) — the server exits immediately.
For my use case, I need a permanently running MCP server (or long-lived transport) that stays alive and can accept connections at arbitrary times.

## Use case

I’m building a multi-agent system using Google ADK, deployed in a Kubernetes/Quarkus 

[Read the thread](https://github.com/GreptimeTeam/greptimedb-mcp-server/issues/23) · 2025-12-09 · closed · external user · 3 comments

### `mcp>=1.8.0` resolves to incompatible MCP SDK 2.x

## Description

In docker image python:3.13-slim, a fresh installation of `greptimedb-mcp-server==0.5.1` now installs MCP Python SDK 2.x because the package metadata declares only:

    mcp>=1.8.0

MCP SDK 2.0 satisfies this constraint, but greptimedb-mcp-server still imports the MCP SDK v1 FastMCP API:

    from mcp.server.fastmcp import FastMCP

FastMCP was removed/replaced in MCP SDK 2.x, so the server fails at startup.

## Error

    ModuleNotFoundError: No module named 'mcp.server.fastmcp'

[Read the thread](https://github.com/GreptimeTeam/greptimedb-mcp-server/issues/43) · 2026-08-15 · closed · external user · 1 comment

### Glama listing is missing Dockerfile

Your MCP server is currently listed on the [Glama MCP directory](https://glama.ai/mcp/servers/GreptimeTeam/greptimedb-mcp-server), but it is not available for others to use because it does not have a Dockerfile.

It takes only a few minutes to fix this:

1. Go to your server's listing: [GreptimeTeam/greptimedb-mcp-server](https://glama.ai/mcp/servers/GreptimeTeam/greptimedb-mcp-server)
2. Click "Claim" to verify ownership.
3. Once claimed, navigate to the [admin `Dockerfile` page](https://glama.

[Read the thread](https://github.com/GreptimeTeam/greptimedb-mcp-server/issues/11) · 2025-04-22 · open · external user · 1 comment

### Query data desensitization

Such as deleting passwords and user information, etc.

[Read the thread](https://github.com/GreptimeTeam/greptimedb-mcp-server/issues/6) · 2025-03-24 · closed · 1 comment

### Migrate to MCP Python SDK 2.x

## Context

#43 was stopped by pinning `mcp>=1.8.0,<2` (released as 0.5.2). That is a stopgap: **MCP Python SDK v1.x entered maintenance mode on 2026-07-28 and now only receives security fixes.** The 1.x line lives on the `v1.x` branch. Staying there means no new protocol revisions and, eventually, no fixes at all.

This issue tracks migrating to MCP Python SDK 2.x.

## What v2 changes

v2 is both an SDK rewrite and support for the **2026-07-28 protocol revision**. A single `MCPServer` serves bo

[Read the thread](https://github.com/GreptimeTeam/greptimedb-mcp-server/issues/44) · 2026-08-16 · open · 0 comments

### opt-in/out specific tools from tool set

for example, only enable pipeline-related tools on one mcp instance, to reduce unrelated context. it can be provided as a configuration to this mcp itself (`args`).

[Read the thread](https://github.com/GreptimeTeam/greptimedb-mcp-server/issues/31) · 2025-12-16 · open · 0 comments

### authorization parameter

allowing access protected dataset via this MCP

[Read the thread](https://github.com/GreptimeTeam/greptimedb-mcp-server/issues/30) · 2025-12-16 · open · 0 comments

### rename `explain_query` tool to `analyze_query`

for better describing what that tool does

[Read the thread](https://github.com/GreptimeTeam/greptimedb-mcp-server/issues/29) · 2025-12-16 · open · 0 comments

## Most recent

### Improve observability

* metrics for calling
* traces

[Read the thread](https://github.com/GreptimeTeam/greptimedb-mcp-server/issues/28) · 2025-12-11 · open · 0 comments

### Audit log for commands

Implement audit logging for MCP commands.

[Read the thread](https://github.com/GreptimeTeam/greptimedb-mcp-server/issues/26) · 2025-12-10 · closed · 0 comments

### Enhance security

Enhance security:

* SQL Injection
* Dangerous SQL execution
* Audit logs
* ...

[Read the thread](https://github.com/GreptimeTeam/greptimedb-mcp-server/issues/14) · 2025-05-21 · closed · 0 comments

The remaining reports are on [the project's issue tracker](https://github.com/GreptimeTeam/greptimedb-mcp-server/issues).