Strata
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STRATA_REPO_PATH | Yes | Path to your LookML repository. | |
| STRATA_USAGE_FIXTURE | No | Path to usage facts fixture JSON (optional, for offline mode). | |
| STRATA_SCHEMA_FIXTURE | No | Path to schema facts fixture JSON (optional, for offline mode). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| strata_query_fieldD | – |
| strata_list_orphansD | – |
| strata_explore_depsD | – |
| strata_ir_statusD | – |
| strata_usage_summaryD | – |
| strata_dead_code_registerD | – |
| strata_pdt_costsD | – |
| strata_schema_driftD | – |
| strata_validation_scopeC | Determine blast radius for changes (impacted_views, impacted_explores, impacted_fields). |
| strata_impactB | Get the downstream impact of a physical table (physical_table, views, explores, fields). |
| strata_find_fieldB | Search for fields matching a query string across all views (query, kind, matches, count). |
| strata_view_sourcesC | List views and their resolved physical tables (model_filter, views, count). |
| strata_navigateA | Classify a ticket anchor and return a full navigator brief in one call. anchor: BQ table, field name, view, explore, or .lkml filename. Returns the views/explores/fields it touches with source_file:source_line citations, plus an inferred change type and what-to-touch list when ticket is set. |
| strata_list_skillsA | List available skills (name, domain, mode, complexity, trigger). |
| strata_skillA | Get the full SKILL.md content for a specific skill. |
| strata_conductor_statusA | Get the current Conductor workflow status (active_slice, next_steps, latest_handoff). |
| strata_chart_templatesA | List available Vega-Lite chart templates (name, mark). |
| strata_render_chartC | Render a chart using a Vega-Lite template and JSON data (path, status). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/G-Schumacher44/strata-oss'
If you have feedback or need assistance with the MCP directory API, please join our Discord server