Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Write TechFabric posts from your agent. Walk through posts, compare studies, check readiness.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://www.techfabric.com/mcp터미널에서 이 명령어를 실행하세요
claude mcp add --transport http techfabric https://www.techfabric.com/mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"techfabric": {
"url": "https://www.techfabric.com/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"techfabric": {
"type": "http",
"url": "https://www.techfabric.com/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://www.techfabric.com/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
도구 이름과 설명은 서버가 2026년 11월 7일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.
searchSearch 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 eng
get_pageOne 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
list_postsTechFabric'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 bu
get_servicesEvery 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_postInteractive: 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
compare_case_studiesInteractive: 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
assess_databricks_readinessInteractive: 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
quiz_meInteractive: 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 lin
visualizeInteractive: draw your answer as a card the reader can use: a comparison with a verdict, a plan as steps, a calculator whose chart follows its sliders, a quiz, a table, a diagram. Write it as an A2UI v0.9.1 document; the tool checks that it will draw (a document that won't comes
get_briefRequires 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
lint_draftRequires 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
check_draftRequires 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 (judge, slop classifier, fact-check), about a minute; call it after lint_draft passes, never to iterate. Each call waits
submit_draftRequires 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 de
update_draftRequires 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 se
list_draftsRequires 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 th
get_statusRequires 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
review_before_publishingRequires 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 ' ' now? (yes/no)") with a one-time confirmation for this exact saved text and its checks (used onc
publish_draftRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). Publish one of your drafts to techfabric.com, only after the engineer confirms, once check_draft with the id has passed on exactly the saved text. The first call publishes nothing: with the draft card showing
preview_draftRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). Interactive: show one of your drafts here. Call it whenever the engineer asks to show, see or open the preview, to show it here, or what the draft looks like (for example: "show me the preview", "show it here"
revise_postRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). Open a revision of a post that is live on techfabric.com, by its URL or slug: only its author or the blog's editor. The revision's draft starts as the live text, with its own preview; then the same loop: get_s
start_postRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). Start here when asked to write, draft or start a blog post or case study for techfabric.com, before writing anything, even inside the techfabric-web repository (never a local file): brainstorm mode (one questi
check_outlineRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read, about a millisecond, free: an outline (title options, the opening's two sentences, four to six sections with a line each, the diagram, the FAQ questions; a case study's four sections) against the title
propose_editsRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). Propose changes to a filed draft as a redline the engineer decides on: each change a passage of the saved markdown (find, exactly as it is), what you propose instead (replace) and why (reason), at most 12 chan
apply_editsRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). The engineer's decision on a proposal (propose_edits): the changes they accepted are applied to the saved text and saved (as update_draft saves), the rule-based checks run at once and the full check starts in
ask_authorRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). One question only the engineer can answer (what was measured, who it was for, what happened): returned for you to ask in chat (or, with form: true, asked in a form where the client shows one); call again with
social_post_kitRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read: what your agent needs to draft a LinkedIn post about a published techfabric.com post, any post on the site. Its key points and first-hand sentences, its link with the LinkedIn campaign, the engineer's
lint_socialRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read: the site's writing rules and the social rules on a LinkedIn post's text (the AI tells, the slop, claims, announcement openers, engagement bait, hashtags), its length, what shows before "see more", and,
reddit_post_kitRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read: what your agent needs to draft a Reddit post or thread answer in your own voice, from a published techfabric.com post or your own notes. The subreddit's rules, the frame (a plain title; first person; t
post_performanceRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read: how one of your own published posts is doing in Google (the blog's editor: any post). Search Console's clicks, impressions, CTR and average position for the last 28 days against the 28 before, the sear
suggest_links_and_topicsRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read: the pages of ours a draft or post should link (posts, services, solutions and case studies sharing its distinctive words), each with why and where (the section, the paragraph and a phrase for the ancho
preview_diagramRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read: every ```mermaid block in a post (or one mermaid source), as the site will treat it. For each: its lines in the post, its caption, whether the site's mermaid parses it (with the error and its line in t
get_brief_poolRequires a TechFabric engineer's Microsoft sign-in (scope blog.write), and only the site owner's is accepted (the Fabric Agents brief automation runs as him). A read: the briefs proposed and not yet taken, the competitor-gap and backlog searches no post or idea covers yet, the 30
propose_briefRequires a TechFabric engineer's Microsoft sign-in (scope blog.write), and only the site owner's is accepted (the Fabric Agents brief automation runs as him). Adds one brief to the pool get_brief offers engineers, first and matched to their work: topic, why (the evidence), angle,
open_editorRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). When the engineer asks to open or edit a draft, or one of their published posts, in the browser: a link to the browser editor that works once and expires in 15 minutes. Show it to them as a link and say so; ne
request_image_uploadRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). Adds an image to one of your own drafts without the browser editor: returns a one-time upload URL and its Authorization header (15 minutes, one PNG, JPEG, WebP or GIF file of the type given, up to 10 MB), and
place_imageRequires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read: the Markdown for an image already uploaded to your draft, ``, and with markdown the post with it in after the paragraph `after` names (or at the end) and the image rules read on i
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 8일 점검
레지스트리 이름이 도메인 techfabric.com 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
1343ms 만에 응답(HTTP 200)
로그인 필요 없음
도구 설명 36개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.6.0)은 11일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, MONS
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Build and adjust your clients' MONS training plans: programs, templates, exercises, sets, reps.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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.
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.
| File | What it is |
|---|---|
server.json | The server's entry in the official MCP Registry, copied as published |
glama.json | Maintainer list for Glama |
icon.png, icon-light.png | The TechFabric mark at 256 px, for dark and light backgrounds |
LICENSE | Apache-2.0, for these files only |
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.
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
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.
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 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"
In ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:
{
"mcpServers": { "techfabric": { "url": "https://www.techfabric.com/mcp" } } }
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" } } }
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"] } } }
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.
Four read tools work for anyone:
| Tool | What it does |
|---|---|
search | Searches the published site (blog posts, service and solution pages, case studies, city pages and events), best first |
get_page | Reads one published page as Markdown, with its title, description, dates, author, tags and FAQs |
list_posts | Lists blog posts, newest first, by tag, author or date |
get_services | Lists every service, solution, accelerator and product page, with the summary the live page gives |
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.
| Tool | What it does |
|---|---|
get_brief | Today's topic for a daily draft, held for the signed-in engineer for 24 hours |
start_post | Seven questions about the engineer's work and its reader, asked before anything is written |
check_outline | Checks an outline's title, opening, headings and FAQ before any prose |
lint_draft | Runs the site's rule-based checks on a draft's Markdown in about a second, each finding naming its passage |
check_draft | Runs the site's full readiness checks, the same ones the browser editor runs before publishing |
submit_draft | Files a post or case study under the engineer's own byline, with a preview |
update_draft | Saves a new version of one of the engineer's own drafts |
list_drafts | The engineer's drafts, newest first, each with its state and next step |
get_status | Where one draft stands: its state, what's failing, its preview and, once live, its link |
preview_draft | Shows a draft as techfabric.com will render it, as an interactive app in hosts that support MCP Apps |
preview_diagram | Parses each mermaid diagram in a post the way the site does, and says what the diagram rules flag |
suggest_links_and_topics | Pages of ours a draft should link, and unanswered searches that fit the engineer's work |
review_before_publishing | Whether a draft may publish, and the question to ask the engineer. Changes nothing |
publish_draft | Publishes one of the engineer's own drafts once its checks pass, and only after they confirm |
revise_post | Opens a revision of a live post as a draft with its own preview, for its author or the blog's editor |
post_performance | Search Console's clicks, impressions and position for a published post, and what to improve |
social_post_kit | What an agent needs to draft a LinkedIn post about a published post |
lint_social | The site's writing rules and the social rules, run on a LinkedIn post |
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.
Anyone:
A signed-in TechFabric author:
/techfabric:write-post how we cut our Lakeflow job's cold start/techfabric:statusReading 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.
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.