Looker
Explore governed business data and LookML models through the Looker-managed MCP server.
Tools
30 available tools
Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.
30 tools found.
Dev mode
Tool name:
dev_modeAllows toggling the Looker IDE session between Development Mode and Production Mode.
Generate embed URL
Tool name:
generate_embed_urlGenerates a signed, private embed URL for specific Looker content, allowing users to access it directly.
Get connection databases
Tool name:
get_connection_databasesRetrieves a list of databases available through a specified Looker connection.
Get connection schemas
Tool name:
get_connection_schemasRetrieves a list of database schemas available through a specified Looker connection.
Get connection table columns
Tool name:
get_connection_table_columnsRetrieves a list of columns for one or more specified tables within a given database schema and connection.
Get connection tables
Tool name:
get_connection_tablesRetrieves a list of tables available within a specified database schema through a Looker connection.
Get connections
Tool name:
get_connectionsRetrieves a list of all database connections configured in the Looker system.
Get dashboards
Tool name:
get_dashboardsSearches for saved dashboards in a Looker instance.
Get dimensions
Tool name:
get_dimensionsRetrieves a list of dimensions defined within a specific Looker explore.
Get explores
Tool name:
get_exploresRetrieves a list of explores defined within a specific LookML model.
Get filters
Tool name:
get_filtersRetrieves a list of "filter-only fields" defined within a specific Looker explore.
Get lookml tests
Tool name:
get_lookml_testsReturns a list of tests which can be run to validate a project's LookML code and/or the underlying data, optionally filtered by the file id.
Get looks
Tool name:
get_looksSearches for saved Looks (pre-defined queries and visualizations) in a Looker instance.
Get measures
Tool name:
get_measuresRetrieves a list of measures defined within a specific Looker explore.
Get models
Tool name:
get_modelsRetrieves a list of available LookML models in the Looker instance.
Get parameters
Tool name:
get_parametersRetrieves a list of parameters defined within a specific Looker explore.
Get project directories
Tool name:
get_project_directoriesRetrieves the list of directories within a specified LookML project.
Get project file
Tool name:
get_project_fileRetrieves the raw content of a specific LookML file from within a project.
Get project files
Tool name:
get_project_filesRetrieves a list of all LookML files within a specified project, providing details about each file.
Get projects
Tool name:
get_projectsRetrieves a list of all LookML projects available on the Looker instance.
Health analyze
Tool name:
health_analyzeCalculates the usage statistics for Looker projects, models, and explores.
Health pulse
Tool name:
health_pulsePerforms various health checks on a Looker instance.
Health vacuum
Tool name:
health_vacuumIdentifies and suggests LookML models or explores that can be safely removed due to inactivity or low usage.
Query
Tool name:
queryRuns a query against a LookML model and returns the results in JSON format.
Query SQL
Tool name:
query_sqlGenerates the underlying SQL query that Looker would execute against the database for a given set of parameters.
Query URL
Tool name:
query_urlGenerates a shareable URL for a Looker query, allowing users to explore the query further within the Looker UI.
Run dashboard
Tool name:
run_dashboardExecutes the queries associated with each tile in a specified dashboard and returns the aggregated data in a JSON structure.
Run look
Tool name:
run_lookExecutes the query associated with a saved Look and returns the resulting data in a JSON structure.
Run lookml tests
Tool name:
run_lookml_testsRuns LookML tests in the project, filtered by file, test, and/or model.
Validate project
Tool name:
validate_projectChecks a LookML project for syntax errors.
Compatibility
Connect Looker to the clients your teams already use
27 AI clients can connect to Looker through Runlayer. Pick one for its setup steps and controls.
Why Runlayer
Why connect Looker through Runlayer?
One approved path
Approve Looker once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.
Fine-grained policy
Control who can use each server, tool, and resource, and under which runtime conditions.
Runtime security
Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.
Audit and observability
Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.
