{ "SchemaVersion": "1", "Kind": "DirectoryIssues", "Slug": "mcp-toolbox-for-databases", "Name": "MCP Toolbox for Databases", "CanonicalUrl": "https://askpod.ai/mcp/mcp-toolbox-for-databases/issues", "ServerUrl": "https://askpod.ai/mcp/mcp-toolbox-for-databases", "IssueTotal": 573, "Held": 24, "Issues": [ { "Title": "feat(source/vertica): add Vertica database source and SQL tools", "Excerpt": "### Prerequisites\n\n- [x] Search the [current open issues](https://github.com/googleapis/mcp-toolbox/issues)\n\n### What are you trying to do that currently feels hard or impossible?\n\nI would like to add Vertica support to MCP Toolbox.\n\nVertica is a columnar analytical database commonly used for large-scale data warehouse and analytics workloads.\n\nCurrently, MCP Toolbox does not have a native Vertica source. Because of this, users cannot:\n\n- Define custom SQL tools backed by Vertica\n- Use Toolbox c", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3883", "PublishedAt": "2026-08-27T11:48:55.000Z", "State": "open", "Comments": 0, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Cloud Build Failure Reporter: toolbox-test-nightly (toolbox-testing-438616) failed", "Excerpt": "Cloud Build Failure Reporter found test failure for [**toolbox-test-nightly (toolbox-testing-438616)** ](https://github.com/googleapis/mcp-toolbox/runs/98464753878) at [527f9911791f5cab55f5b518194d56bf6db1430a](https://github.com/googleapis/mcp-toolbox/commit/527f9911791f5cab55f5b518194d56bf6db1430a). Please fix the error and then close the issue after the **toolbox-test-nightly (toolbox-testing-438616)** test passes.", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3882", "PublishedAt": "2026-08-27T09:13:59.000Z", "State": "open", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Cloud Build Failure Reporter: toolbox-test-on-merge (toolbox-testing-438616) failed", "Excerpt": "Cloud Build Failure Reporter found test failure for [**toolbox-test-on-merge (toolbox-testing-438616)** ](https://github.com/googleapis/mcp-toolbox/runs/98058312312) at [59fb2c42180d1eaf8ac74d099263f9c8b783a1bd](https://github.com/googleapis/mcp-toolbox/commit/59fb2c42180d1eaf8ac74d099263f9c8b783a1bd). Please fix the error and then close the issue after the **toolbox-test-on-merge (toolbox-testing-438616)** test passes.", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3874", "PublishedAt": "2026-08-26T06:14:59.000Z", "State": "open", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "[Feature Request] Allow disabling or configuring export interval for Cloud Trace spans (TraceService/BatchWriteSpans)", "Excerpt": "### Prerequisites\n\n- [x] Search the [current open issues](https://github.com/googleapis/mcp-toolbox/issues)\n\n### Question\n\nIssue Description\n​Environment Details\n​Tool: MCP Toolbox\n​Version: v1.2.0\n​Connector/Database: BigQuery\n​Feature: Telemetry (Tracing)\n​Problem Description\n​After enabling the telemetry feature in mcp-toolbox (v1.2.0) while using the BigQuery tool, the system repeatedly issues span write requests to Google Cloud Trace (google.devtools.cloudtrace.v2.TraceService/BatchWriteSpa", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3862", "PublishedAt": "2026-08-24T05:28:59.000Z", "State": "open", "Comments": 1, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Reloading config file drops all prebuilt tools from server", "Excerpt": "### Prerequisites\n\n- [x] I've searched the current open issues\n- [x] I've updated to the latest version of Toolbox\n\n### Toolbox version\n\n1.9.0\n\n### Environment\n\n1. OS type and version: macOS 26.6.2\n2. How are you running Toolbox: As a downloaded binary (e.g. from `curl -O https://storage.googleapis.com/mcp-toolbox-for-databases/v$VERSION/linux/amd64/toolbox`)\n\n\n### Client\n\n\n\n\n### Expected Behavior\n\nModifying a custom configuration file should trigger a reload and update the custom configs, while", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3859", "PublishedAt": "2026-08-21T20:47:23.000Z", "State": "closed", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "feat(source/db2): add support for IBM Db2 database source and tools", "Excerpt": "### Prerequisites\n\n- [x] Search the [current open issues](https://github.com/googleapis/mcp-toolbox/issues)\n\n### What are you trying to do that currently feels hard or impossible?\n\nWe want to connect AI agents, IDE assistants (such as Google Antigravity, Gemini CLI, Claude Code), and custom production applications to IBM Db2 databases via MCP (Model Context Protocol).\n\nIBM Db2 is widely adopted across enterprise environments (e.g., banking, financial services, retail, and insurance) for mission-", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3858", "PublishedAt": "2026-08-21T20:36:14.000Z", "State": "open", "Comments": 3, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Cloud Build Failure Reporter: toolbox-test-nightly (toolbox-testing-438616) failed", "Excerpt": "Cloud Build Failure Reporter found test failure for [**toolbox-test-nightly (toolbox-testing-438616)** ](https://github.com/googleapis/mcp-toolbox/runs/96371931206) at [c2ada6421f718cb861c7ccd5f0e8cd7e841a407f](https://github.com/googleapis/mcp-toolbox/commit/c2ada6421f718cb861c7ccd5f0e8cd7e841a407f). Please fix the error and then close the issue after the **toolbox-test-nightly (toolbox-testing-438616)** test passes.", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3857", "PublishedAt": "2026-08-21T06:14:03.000Z", "State": "open", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Env var substitution silently skipped when config contains non-ASCII comments", "Excerpt": "### Toolbox version\n\ntoolbox version 1.9.0 (also reproduced with `npx @toolbox-sdk/server`, same version)\n\n### Environment\n\nmacOS (darwin/arm64), binary distributed via npm package `@toolbox-sdk/server`\n\n### Client\n\n`toolbox invoke` CLI, and MCP stdio client\n\n### Expected Behavior\n\n`${VAR}` placeholders outside of YAML comments should always be substituted with\nthe environment variable value, regardless of what characters appear in nearby\ncomments.\n\n### Current Behavior\n\nWhen a config file conta", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3855", "PublishedAt": "2026-08-21T04:43:28.000Z", "State": "closed", "Comments": 1, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Cloud Build Failure Reporter: toolbox-test-nightly (toolbox-testing-438616) failed", "Excerpt": "Cloud Build Failure Reporter found test failure for [**toolbox-test-nightly (toolbox-testing-438616)** ](https://github.com/googleapis/mcp-toolbox/runs/96014156193) at [98c1213269522e4e50f879917bbc95634058da18](https://github.com/googleapis/mcp-toolbox/commit/98c1213269522e4e50f879917bbc95634058da18). Please fix the error and then close the issue after the **toolbox-test-nightly (toolbox-testing-438616)** test passes.", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3850", "PublishedAt": "2026-08-20T06:13:19.000Z", "State": "open", "Comments": 0, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Add a mongodb-list-collections tool to discover collections in a database", "Excerpt": "### Prerequisites\n\n- [x] Search the [current open issues](https://github.com/googleapis/mcp-toolbox/issues)\n\n### What are you trying to do that currently feels hard or impossible?\n\nAfter merging https://github.com/googleapis/mcp-toolbox/pull/3715, a single MongoDB tool config can leave collection out and have the agent supply it at runtime (https://github.com/googleapis/mcp-toolbox/issues/1679). But that only works if the agent already knows the collection name. There's no way for it to ask \"wha", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3848", "PublishedAt": "2026-08-19T19:55:18.000Z", "State": "open", "Comments": 4, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Only run expensive transaction in integration test during nightly.", "Excerpt": "### Prerequisites\n\n- [x] Search the [current open issues](https://github.com/googleapis/mcp-toolbox/issues)\n\n### What are you trying to do that currently feels hard or impossible?\n\nOur integration tests are hitting quota and limit per day since it was running some expensive transaction (such as BigTable Create Instance). We have currently disabled the BigTable create instance integration test (https://github.com/googleapis/mcp-toolbox/pull/3683/changes#diff-8105155a9023b3e9226024914164027972eabc", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3842", "PublishedAt": "2026-08-18T16:52:13.000Z", "State": "open", "Comments": 2, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Cloud Build Failure Reporter: toolbox-test-nightly (toolbox-testing-438616) failed", "Excerpt": "Cloud Build Failure Reporter found test failure for [**toolbox-test-nightly (toolbox-testing-438616)** ](https://github.com/googleapis/mcp-toolbox/runs/95336482327) at [0d4bab81880accd702e5074121a1b17ccb49e01a](https://github.com/googleapis/mcp-toolbox/commit/0d4bab81880accd702e5074121a1b17ccb49e01a). Please fix the error and then close the issue after the **toolbox-test-nightly (toolbox-testing-438616)** test passes.", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3838", "PublishedAt": "2026-08-18T06:12:29.000Z", "State": "closed", "Comments": 1, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "initialize with protocolVersion 2026-07-28 returns -32601 instead of negotiating (behaviour changed in 1.8.0)", "Excerpt": "## Summary\n\nAn `initialize` request carrying `\"protocolVersion\": \"2026-07-28\"` is answered with `-32601 invalid method initialize` on **1.8.0** and **1.9.0**. On **1.7.0** the same request negotiates normally and the server replies with `2025-11-25`.\n\nThe graceful downgrade is otherwise intact — `2026-07-28` is the only value that fails. Unknown versions still negotiate fine, which is what makes this look like a gap rather than a policy: the version is known well enough to be routed, and being k", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3834", "PublishedAt": "2026-08-17T03:48:04.000Z", "State": "closed", "Comments": 4, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Auth (Generic) - Allow ForceIntrospection, pass optional Client ID/Secret on Introspect", "Excerpt": "### Prerequisites\n\n- [x] Search the [current open issues](https://github.com/googleapis/mcp-toolbox/issues)\n\n### What are you trying to do that currently feels hard or impossible?\n\nToday, for JWT validation, it assumes that JWKS validation should be sufficient. However there are some identity providers who require introspection validation on the access_token. Additionally, some identity providers require a client id / client secret are provided as part of the introspection request. \n\n### Sugge", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3832", "PublishedAt": "2026-08-15T18:52:27.000Z", "State": "open", "Comments": 3, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Looker tool to import dashboard from lookml", "Excerpt": "### Prerequisites\n\n- [x] Search the [current open issues](https://github.com/googleapis/mcp-toolbox/issues)\n\n### What are you trying to do that currently feels hard or impossible?\n\nExposing this existing Looker API as a tool is very valuable for non developers to be able to create rich dashboards via AI generated code without needing to execute tons of tools calls to iteratively construct a looker dashboard:\n\nhttps://docs.cloud.google.com/looker/docs/reference/looker-api/latest/methods/Dashboard", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3825", "PublishedAt": "2026-08-14T03:53:57.000Z", "State": "open", "Comments": 0, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Cloud Build Failure Reporter: toolbox-test-on-merge (toolbox-testing-438616) failed", "Excerpt": "Cloud Build Failure Reporter found test failure for [**toolbox-test-on-merge (toolbox-testing-438616)** ](https://github.com/googleapis/mcp-toolbox/runs/94309280705) at [78eb0b8580b0eebf781ba74e4cc12d1f94a7b65b](https://github.com/googleapis/mcp-toolbox/commit/78eb0b8580b0eebf781ba74e4cc12d1f94a7b65b). Please fix the error and then close the issue after the **toolbox-test-on-merge (toolbox-testing-438616)** test passes.", "SourceUrl": "https://github.com/googleapis/mcp-toolbox/issues/3815", "PublishedAt": "2026-08-13T06:36:11.000Z", "State": "closed", "Comments": 1, "Reporter": "Contributor", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "MCP OAuth flow ignores PRM authorization_servers and user is redirected to /authorize → 404", "Excerpt": "### Prerequisites\n\n- [x] I've searched the current open issues\n- [x] I've updated to the latest version of Toolbox\n\n### Toolbox version\n\n1.2.0\n\n### Environment\n\n- **MCP server**: `googleapis/mcp-toolbox` v1.2.0 with `--prebuilt=looker` configured in EKS\n- **Authorization server**: Looker (`https://.com`)\n- **Reproduction date**: 2026-05-22\n\n```\nprm.json: |\n {\n \"resource\": \"https:///mcp\",\n \"authorization_servers\": [\"https://