TechFabric

techfabric.com MCP server

TechFabric's engineers write blog posts and case studies from the coding agent they already use, with the repository and context it already has. This MCP server is how: the agent takes today's brief, runs the site's checks, files the draft under the engineer's byline and, once the engineer has read the preview and said yes, publishes it.

Anyone can use it to search and read the site, without signing in.

https://www.techfabric.com/mcp

It's a remote server over Streamable HTTP, so there's nothing to install, and it's free. The four read tools need no account. The author tools need a TechFabric engineer's Microsoft sign-in, which the server starts through OAuth the first time one is called.

The same team publishes the Databricks Field Guide and its MCP server, and the TechFabric Toolkit for Databricks, a free Chrome extension.

What's in this repository

Descriptor files, so MCP directories have a repository to list. The official MCP Registry entry names this repository, and GitHub's MCP Registry shows this README in Copilot. The server's code isn't here and isn't open source.

The live server and the registry are the source of truth. If this README and the server's tools/list ever disagree, the server is right. A weekly GitHub Action compares server.json with the registry and opens a pull request when the entry has changed.

Add it to your agent

Claude Code

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

Add --scope user to have it in every project. TechFabric authors should install the Claude Code plugin instead, which adds the server, the eleven commands and a writing skill in one go, and asks before every publish:

claude plugin marketplace add Fabric-Pro/techfabric-claude-plugin && claude plugin install techfabric@techfabric

Claude Desktop and claude.ai

Open Customize, then Connectors, choose Add and then Add custom connector. Name it techfabric, paste https://www.techfabric.com/mcp, keep the authentication settings Claude detects, and choose Add. On a Team or Enterprise plan, an owner may have to add the connector for the organisation first.

ChatGPT

At chatgpt.com/plugins, choose + and then Add custom MCP server. Name it techfabric, paste the URL under Connection, choose OAuth for authentication, and create it as a plugin. In a chat, type @ and pick techfabric. If Add custom MCP server isn't there, your workspace's admin has to turn it on.

Codex

codex mcp add techfabric --url https://www.techfabric.com/mcp

Codex may start a sign-in when you add it. Readers can skip it, because every read tool works without one. By hand, in ~/.codex/config.toml:

[mcp_servers.techfabric]

url = "https://www.techfabric.com/mcp"

Cursor

In ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:

{

"mcpServers": { "techfabric": { "url": "https://www.techfabric.com/mcp" } } }

VS Code

In .vscode/mcp.json, then start it from that file or the MCP view. The tools show up in Copilot's agent mode, and the commands as /techfabric.write-post and so on in Copilot Chat.

{

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

GitHub Copilot

In VS Code, use the configuration above. Copilot CLI saves the server to ~/.copilot/mcp-config.json, for every project:

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

Copilot's coding agent on github.com takes it in the repository's Settings, under Copilot and MCP servers. The coding agent can't complete an OAuth sign-in, so give it the read tools:

{

"mcpServers": { "techfabric": { "type": "http", "url": "https://www.techfabric.com/mcp", "tools": ["search", "get_page", "list_posts", "get_services"] } } }

Anything else

Point the client at the URL with the Streamable HTTP transport. Gemini CLI, OpenCode and Fabric Agents each have their own steps in the setup guide.

Tools

Four read tools work for anyone:

They answer only from published, indexable pages, so drafts and previews never show up in a result.

Eighteen author tools need a TechFabric engineer's Microsoft sign-in. Called anonymously, each answers with the sign-in challenge.

Commands

The server ships eleven prompts, which most agents show as slash commands: write-post, write-case-study, check, preview, publish, revise, status, blog-post-template, case-study-template, linkedin-post and performance. Each gives the agent the steps in order and points it at the house rules. In Claude Code with the plugin they're /techfabric:write-post and so on. The setup guide has the equivalents for Codex, Cursor, Gemini CLI and Fabric Agents.

Things to ask

Anyone:

• "What does TechFabric do with Databricks? Use the techfabric MCP server."
• "Find TechFabric's blog posts about MCP and summarise the newest one."
• "Read techfabric.com's page on cloud migration and list the questions its FAQ answers."

A signed-in TechFabric author:

• /techfabric:write-post how we cut our Lakeflow job's cold start
• "Write a TechFabric blog post about how we . Ask me for anything you don't know instead of inventing it, and give me the preview link when it's filed."
• /techfabric:status

Sign-in, limits and privacy

Reading needs no account and sets no cookie. The author tools are for TechFabric's own blog authors, who sign in with their Microsoft account in the techfabric.com tenant and must be on the blog's author list. No other tenant is accepted, and a sign-in lasts up to 30 days.

Anonymous callers get 300 calls an hour per IP address. Signed-in authors get 600 an hour, with lower caps on check runs, submissions, saves and publishes. Past a limit the server answers HTTP 429 with a Retry-After header.

Neither the read tools nor the log keep what you searched for or read: a log line names the tool and the protocol revision, never its arguments, and no read call reaches a language model. When an author signs in to write, the server keeps the text they check, file or save, with their address against it. The privacy policy covers the rest.

It speaks MCP revision 2026-07-28, and clients still on 2025-11-25 are served on the same URL. In the official registry it's com.techfabric/techfabric.

Links

• Setup guide for both TechFabric MCP servers, with every tool, resource and limit
• The official MCP Registry entry
• Claude Code plugin
• The Databricks Field Guide MCP server, TechFabric's other one, for Databricks questions
• TechFabric's blog
• What TechFabric does
• Talk to an engineer

License

The files in this repository are under the Apache License 2.0, copyright Tech Fabric LLC. The site's content and the server itself aren't covered by it.