Weld
Start free

Storepoint Connector

A store locator app, customized for different websites

Start for free
4.8 on G2
Weld · Data Sources
StorepointLive
custom_fieldSynced
location_custom_fieldSynced
locationSynced
location_tagSyncing
Lands insnowflakebigquerydatabricksAgent context over MCP
How it works

Set up in minutes.
No code, no maintenance.

Storepoint

Storepoint

Data source

Authenticating...
Ready to connect
Overview

Storepoint in your warehouse.
Ready for your agents.

A store locator app, customized for different websites Weld's Storepoint connector is fully managed: it extracts data from Storepoint, loads it into your warehouse, and keeps it in sync. The data lands in a clean, documented schema with agent context attached, so analysts can query it with SQL or dbt, and agents can query it over the Weld MCP server without guessing at tables or joins.

AgentsQuery over MCPYour warehouse4 tables, with agent contextWeldExtract, load, keep in syncStorepointSource
Agent context

Storepoint data schema.
The map your agents read.

Every table, field and relationship Weld syncs from Storepoint is served to agents as context over MCP, so they pick the right tables and join on the right keys.

tables
4
fields
33
relationships
1
Open the schema explorer Open the full schema explorer
Weld MCP server

Ask your agent.
It already knows Storepoint.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Storepoint context, finds the tables it needs and queries your warehouse.

  • Agent contextStorepoint tables, fields and joins
  • QuerySQL against your warehouse
  • OperateCheck, rerun and refresh syncs
Set up the MCP serverClaudeCursorChatGPTGemini
Claude CodeOpus 5
>

How many location_custom_field rows do we have per location? Use our Storepoint data.

Reading the Storepoint context first, so the query uses the right tables and keys.

●weld·search_available_references
⎿raw.storepoint.location_custom_field
raw.storepoint.location
+ 2 more Storepoint tables
●weld·get_reference_schema
⎿location_custom_field · 4 columns
joins location on location_id
●weld·run_query
⎿select j.id, count(*) from {{raw.storepoint.location_custom_field}} l
join {{raw.storepoint.location}} j on l.location_id = j.id
group by 1
submitted
●weld·get_query_status
⎿DONE
●weld·get_query_result
⎿rows returned
✓Answered from Storepoint data in your warehouse
>Ask about your Storepoint data
Destinations

Load Storepoint into any warehouse.
Set up in minutes, no code.

Resources

Everything you need.
To get started.

MCP server

Connect your agents

Set up Claude, Cursor, ChatGPT or Codex against your Weld workspace.

Weld Connect API

Build custom connectors

Use the Weld Connect API to build and publish your own connector.

FAQ

Common questions

Answers to frequently asked questions about Weld connectors.

Weld Connect API

Set it up in code.
One REST API.

Use the Weld Connect REST API to create Storepoint connections, configure ELT syncs, and manage pipelines entirely through code. Built for embedding, automation, and CI/CD workflows.

Explore Weld ConnectAPI reference
POST/elt_syncs
▌
FAQ

Common questions.
About connectors.

Something not covered here? A data engineer can walk through your setup with you.

Talk to us

Put your Storepoint data to work.

Connect Storepoint, pick a warehouse, and your agents can query it today. Free for 14 days, no credit card.

StorepointSource
WeldWeld
MCPAgents
Start for freeTalk to us
Connectors

Explore more connectors.
300+ and counting.

View all connectors