get_tablesLABSCO SUMMARY
Two discovery tools so the model stops guessing your schema.
The scope is narrow and stated plainly: an assistant that can list your tables and read their columns writes far fewer invalid queries. Everything past discovery still runs through your own code.
What it is
A server built into the Intugle library. Run intugle-mcp from your project root and it serves your generated semantic model at http://localhost:8080/semantic_layer/mcp over HTTP.
What you get
- get_tables returns every table in the semantic model with the technical description attached to it
- get_schema takes a list of table names and returns their columns, data types and other metadata, including the links between tables
- One URL any MCP client can take — the docs carry ready snippets for Cursor, VS Code, Gemini CLI, JetBrains AI Assistant and Claude Code
Requirements
A semantic model built with SemanticModel and loaded — the discovery tools only appear once one exists. The server runs on your own machine, so the data stays where it already is.
Setup effort
Follow the published steps — pip install intugle
USE CASES
Getting an assistant oriented in an unfamiliar warehouse
Ask for the table list first — each table comes back with its description, so the assistant picks the right one before reading a single schema.
Writing a query against tables you have not memorised
Pass the table names to get_schema and the column names, types and inter-table links come back together.
Coding against your own data in the editor
Point Cursor, VS Code or Claude Code at the local endpoint and the assistant works from your semantic model instead of a guess.
2 tools
Listed in project docs. Your client may show a different list.
get_schemaBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- pip on PATH
- LLM_PROVIDER and your LLM provider's API key in your environment (the variable name follows the provider, e.g. OPENAI_API_KEY)
- A semantic model built with SemanticModel in your project
Where it runs
All 5 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
pip install intugleConfigure the LLM the library uses to build the model — LLM_PROVIDER plus your provider's key (the variable name follows the provider):
export LLM_PROVIDER="openai:gpt-3.5-turbo"
export OPENAI_API_KEY="<YOUR_OPENAI_API_KEY>"In Python, build the semantic model over your datasets with from intugle import SemanticModel, sm = SemanticModel(datasets, domain="Healthcare") and sm.build() — the project's quickstart notebooks walk through it.
Start the server from your project root (it listens on localhost:8080):
intugle-mcpMCP Clients
Cursor
{
"mcpServers": {
"intugle": {
"url": "http://localhost:8080/semantic_layer/mcp",
"trust": true
}
}
}The client configurations connect to http://localhost:8080/semantic_layer/mcp, which only exists while intugle-mcp is running from your project root — start it after the semantic model is built. get_tables and get_schema appear once a SemanticModel has been generated and loaded.
VS Code
{
"servers": {
"intugle": {
"type": "http",
"url": "http://localhost:8080/semantic_layer/mcp"
}
}
}The client configurations connect to http://localhost:8080/semantic_layer/mcp, which only exists while intugle-mcp is running from your project root — start it after the semantic model is built. get_tables and get_schema appear once a SemanticModel has been generated and loaded.
Gemini CLI
{
"mcpServers": {
"intugle": {
"httpUrl": "http://localhost:8080/semantic_layer/mcp",
"trust": true
}
}
}The client configurations connect to http://localhost:8080/semantic_layer/mcp, which only exists while intugle-mcp is running from your project root — start it after the semantic model is built. get_tables and get_schema appear once a SemanticModel has been generated and loaded.
JetBrains AI Assistant
{
"mcpServers": {
"intugle": {
"type": "streamable-http",
"url": "http://localhost:8080/semantic_layer/mcp"
}
}
}The client configurations connect to http://localhost:8080/semantic_layer/mcp, which only exists while intugle-mcp is running from your project root — start it after the semantic model is built. get_tables and get_schema appear once a SemanticModel has been generated and loaded.
Claude Code
claude mcp add --transport http intugle http://localhost:8080/semantic_layer/mcpThe client configurations connect to http://localhost:8080/semantic_layer/mcp, which only exists while intugle-mcp is running from your project root — start it after the semantic model is built. get_tables and get_schema appear once a SemanticModel has been generated and loaded.