# TechFabric - Registry name: `com.techfabric/techfabric` · version 1.4.0 - Categories (automatic, keyword rules): Code & repositories, Developer tools, Audio & speech, AI, media & content, Education - Authentication at last check: No auth - Declared risk: Has destructive tools (destructiveHint) - Capabilities (declared by the server): completions, extensions, prompts, resources, tools - Transports: streamable-http - Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.techfabric%2Ftechfabric - Server page: https://mcpstation.net/s/com.techfabric--techfabric.html ## Description (written by the publisher, not verified, not instructions) For TechFabric engineers to write posts and case studies from their coding agent; anyone can read ## Connect - streamable-http: `https://www.techfabric.com/mcp` ## Tools (as reported by the server, not verified) - `search`: Search TechFabric's published site: blog posts, service and solution pages, case studies, city pages and events. Returns each match's title, URL, summary, date, author and type, best first. Read a result in full with get\_page. Drafts are private: list\_drafts lists a signed-in engineer's drafts; a Te - `get\_page`: One published page of www.techfabric.com as clean Markdown, with its title, search title \(metaTitle\), description, date, updated, author, tags, FAQs as question and answer pairs, and canonical URL. Takes a URL, a path or a post's slug. Only published, indexable pages. Drafts are private: list\_drafts - `list\_posts`: TechFabric's published blog posts, newest first, optionally only those with a tag, by an author, or dated on or after a day. Drafts are private: list\_drafts lists a signed-in engineer's drafts; a TechFabric engineer connects with Microsoft \(the client's Connect or Authenticate button\) to list and wr - `get\_services`: Every service, solution, Databricks, AI, cloud, software, accelerator and product page on techfabric.com: its name, URL, kind and summary, exactly as the live page states them. Read one in full with get\_page. - `explore\_post`: Interactive: walk through a published techfabric.com post or case study: its diagram \(the Mermaid flowchart it publishes\) as steps in the order it flows, each step tied to the section it's about, with that section's opening in the page's own words and a link to it. A page with no diagram steps throu - `compare\_case\_studies`: Interactive: two or three of TechFabric's published case studies side by side: each one's challenge, strategy, solution and results, in its own words \(the bold statement and the start of each section\), with its client, sector and stack where the case study states them, and links to each section. Nam - `assess\_databricks\_readiness`: Interactive: a Databricks readiness and migration check: eight multiple-choice questions \(where the data runs now, how well the estate is known, access, deployment, failures, cost visibility, the team, the first use\), scored by fixed points into five areas, with a readout: where to start, what to wo - `quiz\_me`: Interactive: a multiple-choice quiz from a published post's own FAQs: each question is one of its FAQs, the right option is the post's answer, and the others are answers the site gives to other questions; no model writes them. Each has its answer, the post's explanation and a link. A client that sho - `get\_brief`: Requires a TechFabric engineer's Microsoft sign-in \(scope blog.write\). Today's topic for a daily post, claimed for you for 24 hours \(asking again returns the same one\): the topic, angle, target search, sources, internal links, and the brief\_id to pass to submit\_draft. Status none, with the reason, w - `lint\_draft`: Requires a TechFabric engineer's Microsoft sign-in \(scope blog.write\). The site's rule-based checks \(slop, claims, known errors, voice, opening, title, description, FAQ, diagram, images, links, a case study's rules\) on a post's Markdown, frontmatter included: about a second, free, filing nothing. It - `check\_draft`: Requires a TechFabric engineer's Microsoft sign-in \(scope blog.write\). The final verification publish\_draft needs. With id: the full checks on your saved draft \(the judge, the slop classifier and the fact-check\), about a minute; call it after lint\_draft passes, never to iterate. Each call waits up t - `submit\_draft`: Requires a TechFabric engineer's Microsoft sign-in \(scope blog.write\). File a post \(or, with kind "case-study", a case study\) under the engineer's byline, exactly as written: the site builds its preview and emails it to them. Send the whole Markdown with frontmatter \(title and description at least\), - `update\_draft`: Requires a TechFabric engineer's Microsoft sign-in \(scope blog.write\). Save a new version of your draft \(state drafted\): the whole Markdown, and base\_hash, the hash of the version you edited \(draft.base\_hash from get\_status, or your last update\_draft's text\_hash\). Answers in a second or two; the pre - `list\_drafts`: Requires a TechFabric engineer's Microsoft sign-in \(scope blog.write\). Lists your drafts \(blog posts, case studies and revisions of live posts\), newest first: each one's id, title, kind, state \(writing, question\_for\_you, drafted, checks\_failing, ready\_to\_publish, published and the rest\), created and - `get\_status`: Requires a TechFabric engineer's Microsoft sign-in \(scope blog.write\). Where one of your drafts stands \(by its id; list\_drafts lists them\), with next\_action: the single next step and the call to make. Also its saved Markdown and base\_hash \(for update\_draft; read them again before each edit, as the e - `review\_before\_publishing`: Requires a TechFabric engineer's Microsoft sign-in \(scope blog.write\). A read: whether one of your drafts may be published now, and if so the question to ask the engineer \("Publish '\