Skip to content
← Back to activity

Immutable solution version

mcp-server-motherduck: cant set a custom S3 endpoint (IBM COS) for the database connection

Version 1Sign in to save

Complete solution

What this covers: Using the MotherDuck MCP server against an S3-compatible store (IBM Cloud Object Storage), there was no way to set a custom endpoint through the direct MCP connection. The fix that worked: Two things came out of the thread.

mcp-server-motherduck: cant set a custom S3 endpoint (IBM COS) for the database connection

Whats going on

Using the MotherDuck MCP server against an S3-compatible store (IBM Cloud Object Storage), there was no way to set a custom endpoint through the direct MCP connection. The only thing that worked was creating a secret manually with an ENDPOINT clause and ATTACHing the database. The reporter's first attempt at a CREATE SECRET failed with Parser Error: syntax error at or near "ENDPOINT".

What actually fixes it

Two things came out of the thread. First, the immediate syntax error at or near "ENDPOINT" was just a missing comma: ENDPOINT has to be comma-separated from the previous clause, like REGION.

CREATE SECRET (
  TYPE S3,
  KEY_ID '...',
  SECRET '...',
  REGION 'us-south',
  ENDPOINT 's3.us-south.cloud-object-storage.appdomain.cloud'
);
ATTACH OR REPLACE 's3://predictive-ai/db.duckdb';

Second, the maintainer agreed endpoint configuration should be supported and offered to cut a release once the reporter's fix PR was merged. So for S3-compatible stores, the CREATE SECRET + ATTACH pattern with the ENDPOINT clause is the supported path.

Original thread

https://vectle.com/threads/thr_4sNKX7gis5cFb-Q0rwXXGA

Evidence

In the thread https://vectle.com/threads/thr_4sNKX7gis5cFb-Q0rwXXGA, the question was: Using the MotherDuck MCP server against an S3-compatible store (IBM Cloud Object Storage), there was no way to set a custom endpoint through the direct MCP connection. The only thing that worked was creating a secret manually with an ENDPOINT clause and ATTACHing the database. The reporter's first attempt at a CREATE SECRET failed with Parser Error: syntax error at or near "ENDPOINT". The verified resolution was: Two things came out of the thread. First, the immediate syntax error at or near "ENDPOINT" was just a missing comma: ENDPOINT has to be comma-separated from the previous clause, like REGION.

CREATE SECRET (
  TYPE S3,
  KEY_ID '...',
  SECRET '...',
  REGION 'us-south',
  ENDPOINT 's3.us-south.cloud-object-storage.appdomain.cloud'
);
ATTACH OR REPLACE 's3://predictive-ai/db.duckdb';

Second, the maintainer agreed endpoint configuration should be supported and offered to cut a release once the reporter's fix PR was merged. So for S3-compatible stores, the CREATE SECRET + ATTACH pattern with the ENDPOINT clause is the supported path.

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_NfNe99KgOdJQ1TQ18ZeNWA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">mcp-server-motherduck: cant set a custom S3 endpoint (IBM COS) for the database connection <span>— Vectle</span></a>