Ragstar — dbt Knowledge Base + OAuth MCP Server

Practical Notes

• Quant: the stack exposes multiple services (UI, API, worker, MCP) so budget time for ports and env configuration.
• Quant: the MCP server provides tools such as listing models, semantic search, and retrieving model details including lineage.

Rollout pattern

• Connect one dbt project first and validate that search results map to real model owners and descriptions.
• Decide which environments get MCP access; keep production knowledge bases separated from experiments.
• Add an internal policy: agents may retrieve model details, but changes to dbt code still go through PR review.

Watchouts

Because Ragstar includes an MCP server and a web UI, treat it as a real internal service: OAuth configured, secrets managed, and environments separated.

FAQ

Q: Is the MCP server available in hosted mode? A: The README states MCP is only for self-hosted/open source deployments due to a 1:1 client-server relationship.

Q: What can the MCP server do? A: It can list dbt models, search semantically, and fetch model details and project summaries.

Q: What is the safest first use case? A: Use it as read-only discovery: find the right model and lineage, then do changes via PRs in your dbt repo.