list_accountsLABSCO SUMMARY
One tool behind a paid add-on is an early-stage surface — judge it on where it is going, not what it does today.
The interesting thing here is the permission model rather than the tool count: the connection acts within your workspace permissions rather than as a service identity, which is the design you want when the surface eventually grows to touch the warehouse. Take the trial before the add-on, and check what has shipped since — a single-tool endpoint on a data platform is a beginning, not a product.
What it is
Weld is a data platform. Their documented endpoint surface is currently minimal: a single tool listing accounts, operating inside the permissions your workspace already grants you.
What you get
list_accounts. Their walkthrough shows using it from an assistant against your workspace.
Requirements
OAuth or an API key. It requires their premium plan or above, sold as a monthly add-on, with a two-week test available on the entry plan.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Seeing what is connected
List the accounts in your workspace.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth, or an x-api-key header
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://connect.weld.app/mcpRequirements
- OAuth, or an x-api-key header
