Calling tool `get_cratedb_documentation_index` blocks with v0.0.4

[amotl]

Problem

With the most recent release, this invocation blocks.

mcpt call get_cratedb_documentation_index uvx cratedb-mcp==0.0.4 serve

Using the previous version, it works flawlessly.

mcpt call get_cratedb_documentation_index uvx cratedb-mcp==0.0.3 serve

Install

You can install the mcpt and uvx programs like this on a macOS system ¹.

brew tap f/mcptools
brew install mcp uv

Footnotes

1. Or build mcpt from sources at mcptools. ↩

[amotl]

All of those tool invocations are working well, only get_cratedb_documentation_index is blocking.

mcpt call get_table_metadata cratedb-mcp serve

mcpt call get_cluster_health cratedb-mcp serve

mcpt call fetch_cratedb_docs --params '{"link": "https://cratedb.com/docs/guide/_sources/home/index.md.txt"}' cratedb-mcp serve

[amotl]

Apparently, this problem only happens on my machine (macOS), while it works well on CI (Linux)?

[amotl]

I have been able to reproduce the problem also on Linux.

docker run --rm -it golang:1.24-bookworm bash

go install github.com/f/mcptools/cmd/mcptools@latest
apt update && apt install --yes python3-pip
pip install --break-system-packages uv
mcptools call get_cratedb_documentation_index uvx cratedb-mcp==0.0.4 serve

[amotl]

[...] while it works well on CI (Linux)?

It doesn't! This particular test is being skipped on CI.

-- https://github.com/crate/cratedb-mcp/actions/runs/16442799463/job/46467334356#step:8:56

[amotl]

Because the problem exists for all users, the release v0.0.4 has been yanked from PyPI. For the next release, a09c39a is the corresponding fix, while bf94ed2 fixes another related problem why the regression was not detected early by software tests.

• MCP: Fix get_cratedb_documentation_index tool #60

[amotl]

Fixed with release v0.0.5.

mcpt call get_cratedb_documentation_index uvx cratedb-mcp==0.0.5 serve