TechFabric's MCP servers

Databricks Field Guide

What tools does the Databricks Field Guide MCP server have?

Five read-only tools. They search the guide, read a chapter or one section, find code examples, list what Databricks changed lately and list the chapters.

The Databricks Field Guide is what our engineers know about building, running and paying for Databricks. Ask how to add a Unity Catalog row filter, and the agent gets the section that explains it, the SQL function from that section, and the docs.databricks.com pages the section cites. Databricks' documentation stays the authority on syntax and limits.

Sign-in

None. The server is public and read-only, and it has no write tools.

Protocol

MCP revision 2026-07-28 over Streamable HTTP. Clients still on 2025-11-25 are served on the same URL.

Rate limits

60 calls a minute and 300 an hour per IP address.

Freshness

Rebuilt on every deploy of the guide. Every answer carries the commit that built it, each page's last-changed date and how long it may be cached, which is 10 minutes for what's new, 15 for search and an hour for chapters and code.

Registry

com.techfabric.databricks/field-guide, version 1.1.1. MCP Registry entry · Glama listing

The Field Guide's five tools

• search_guideRead

  Search the guide

  The guide sections that answer a Databricks question.

  Returns and parameters +

  Returns

  The chapter sections, margin notes and events that answer a Databricks question, best first, each with a snippet, its URL with the section anchor, and when the page last changed.

  Parameters

  query (required); kind: chapter, note, feature or event; limit 1 to 25, default 10

• get_chapterRead

  Read a chapter

  A chapter or one section as Markdown, code intact.

  Returns and parameters +

  Returns

  A chapter or margin note as clean Markdown with its code intact, or one section of it, plus the outline, the code blocks listed separately, the FAQs, the dates and the docs.databricks.com links it cites.

  Parameters

  slug (required): a slug such as lakebase, a path or any guide URL; section: an anchor or a heading

• get_code_examplesRead

  Find code examples

  SQL, Python, CLI and config blocks for a topic.

  Returns and parameters +

  Returns

  SQL, Python, CLI and config blocks that match a topic, each with the explanation around it, the section it came from and the docs links that section cites.

  Parameters

  topic (required); lang such as sql, python, bash, yaml, json or hcl; limit 1 to 25, default 8

• whats_newRead

  What's new in Databricks

  Recent Databricks changes the guide tracks, newest first.

  Returns and parameters +

  Returns

  Recent Databricks changes the guide tracks, newest first: margin notes, release-stage changes with links to Databricks' documentation and release notes, and chapters updated.

  Parameters

  since (YYYY-MM-DD, default the last 30 days); limit 1 to 200, default 30

• list_chaptersRead

  List chapters

  The table of contents, with each chapter's main sections.

  Returns and parameters +

  Returns

  Every chapter in the guide's order, with its part, summary, dates, URL, Markdown URL and main sections, and the margin notes.

  Parameters

  None

Field Guide resources

• fieldguide://llms.txt

  Every chapter, note and feature page, one line each.

• fieldguide://page/{+path}

  Any published page as Markdown, for example fieldguide://page/guide/lakebase.

Connect

How to connect Claude, Cursor or VS Code to TechFabric's MCP servers

Add the server's URL to your client. Both servers are remote, so there's nothing to install, and the names below are only labels.

claude mcp add --transport http techfabric https://www.techfabric.com/mcp

claude mcp add --transport http databricks-field-guide https://databricks.techfabric.com/mcp

{
  "mcpServers": {
    "techfabric": { "url": "https://www.techfabric.com/mcp" },
    "databricks-field-guide": { "url": "https://databricks.techfabric.com/mcp" }
  }
}

{
  "servers": {
    "techfabric": { "type": "http", "url": "https://www.techfabric.com/mcp" },
    "databricks-field-guide": { "type": "http", "url": "https://databricks.techfabric.com/mcp" }
  }
}

npx mcp-remote https://databricks.techfabric.com/mcp

Reading never asks you to sign in. Writing to techfabric.com is for TechFabric's authors, and its sign-in and workflow are under writing a TechFabric blog post with your own agent.

For TechFabric authors

How to write a TechFabric blog post with your own agent

Your agent writes the post from what you actually did, and the site checks it, builds the preview and leaves publishing to you. Writing needs a techfabric.com Microsoft account that is on the blog's author list.

claude mcp add --transport http --scope user techfabric https://www.techfabric.com/mcp

The workflow, step by step

1. Step 1

   Read the editorial rules

   Your agent reads the editorial_rules resource (techfabric://editorial/rules). It starts with client confidentiality, which decides what the post may say, then gives the frontmatter, this workflow and the house writing rules.

2. Step 2

   Draft from your own work

   Your agent drafts the post, frontmatter and all, from what it knows about your own work, such as the repository you're in and your notes. The frontmatter is required, with a title and a description at least: check_draft, submit_draft and update_draft refuse a post with no frontmatter or no title.

3. Step 3

   Check it and fix the findings

   Your agent runs check_draft, which runs the browser editor's own checks without filing a draft. A full run takes five to ten minutes. Each finding comes back with the exact passage it's about, so the agent fixes those passages and checks again.

4. Step 4

   Submit it under your byline

   Your agent calls submit_draft. The post is filed under your own byline exactly as written. The site sets the author, today's date and draft: true, and adds the reading time if it's missing. It renders the diagrams, draws the cover and share image, builds the branded preview and emails it to you. The agent gets the draft's id back.

5. Step 5

   Follow its status

   Your agent calls get_status with the draft's id, or subscribes to techfabric://drafts/{id}, for the check results, what's still failing, the preview, the editor link and the draft's base_sha.

6. Step 6

   Revise with update_draft

   For revisions your agent calls update_draft with the id, the whole new post and that base_sha. A save commits the text and rebuilds the preview. It runs no checks. update_draft is refused if the draft has changed since that base_sha, or while it's open in the browser editor.

7. Step 7

   Run checks and publish from the editor

   You read the preview, open the editor link and choose Run checks, or Run checks, then publish. Publish needs a check run that passed on exactly the saved text. A check_draft pass doesn't count, and any save after a run means running the checks again. The approve link in the preview email, when it has one, runs every check at approval instead and holds the post if one fails.

Read techfabric.com's editorial rules (the techfabric editorial_rules resource), then write a TechFabric blog post about how we <solved this problem or built this thing>. Draft only from what I actually did and what's in this project; never name a client the rules don't approve, and ask me for any fact you don't have instead of inventing it. Run check_draft and fix every finding, then submit it with submit_draft and give me the preview and editor links.

Troubleshooting

Sign-in refused

The sign-in page says why. If it says your address is not on techfabric.com's author list yet, there's no byline to draft under, so ask Preetham Reddy to add you. If it says only TechFabric's Microsoft accounts or only @techfabric.com accounts can sign in, or that guest accounts can't, you signed in with another Microsoft account; sign in again with your own @techfabric.com one. If it says the app can't connect, the client isn't Claude Code or a Claude custom connector.

A check keeps failing

Open the editor link from get_status. Its checklist shows each failing item with the passage it's about. Fix it there, or have your agent fix it and call update_draft.

Too many calls

Signed in, the limits per hour are 600 calls, 20 new check runs, 6 submissions and 30 saves. Checking text that was already checked doesn't count as a new run.

Anything else

Ask Preetham Reddy, who runs the blog.