Zum Inhalt springen

Verbinde BlackBelt mit deiner KI

BlackBelt betreibt einen öffentlichen MCP-Server: In deinen KI-Client (Claude, Cursor, ChatGPT) eingebunden, kann dein Assistent die Leistungen, Technologien, Seiten und kundenbestätigten Referenzen von BlackBelt direkt abfragen.

In drei Schritten verbinden

  1. Öffne die MCP-Einstellungen deines KI-Clients (Claude Desktop → Settings → Connectors oder Cursor → MCP).
  2. Füge den untenstehenden Streamable-HTTP-Endpunkt als neuen MCP-Server hinzu.
  3. Fertig. Dein Assistent sieht nun die BlackBelt-Werkzeuge — frag zum Beispiel, welche Referenzen wir im Gesundheitswesen haben.

MCP-Endpunkt (Streamable HTTP)

https://blackbelt.hu/api/mcp

Client-Konfiguration — zum Kopieren

{
  "mcpServers": {
    "blackbelt": {
      "type": "http",
      "url": "https://blackbelt.hu/api/mcp"
    }
  }
}

Verfügbare Werkzeuge

Alle 5 öffentlichen Werkzeuge sind NUR LESEND: Sie schreiben nicht, löschen nicht und verlassen unsere eigenen Daten nicht. Eine Anmeldung ist nicht erforderlich.

Das Verzeichnis nennt NAMEN und BESCHREIBUNG der Werkzeuge — es gewährt keinen Zugriff. Die Grenze liegt serverseitig: Die nicht öffentlichen Server weisen jede Anfrage ohne gültige Anmeldung ab, und über die Rechte entscheidet die Rolle der Redakteurin oder des Redakteurs, nicht diese Seite.

Die Werkzeugbeschreibungen liegen auf Englisch vor — der Katalog führt sie bislang nur auf Ungarisch und Englisch.

Öffentlicher Server /api/mcp

Keine Anmeldung nötig — jede und jeder kann ihn einbinden.

  • about_blackbeltread-only

    A short factual company overview and how to get in touch.

  • list_blackbelt_servicesread-only

    The three BlackBelt service divisions and what each covers.

  • list_blackbelt_technologiesread-only

    Technologies and platforms, including the JUDO low-code platform.

  • list_blackbelt_pagesread-only

    The public pages with their layout type (L1-L9), with an optional filter.

  • search_blackbelt_referencesread-only

    Client-confirmed case studies by free-text query and/or industry.

Studio-Server (redaktionell) /api/studio/mcp

ANMELDUNG ERFORDERLICH. Das sind die redaktionellen Werkzeuge: Sie schreiben in die ENTWURFS-Ebene. Seiten und das Menü kann auch der Agent eines angemeldeten Redakteurs veröffentlichen — in zwei Schritten, nachdem der Plan gezeigt wurde und der Redakteur ausdrücklich zugestimmt hat; Artikel veröffentlicht nur ein Mensch in der Studio-Oberfläche.

  • get_home_layoutread-only

    The PUBLISHED home layout's DESIGN TOKENS (the server-side home draft is gone). ⚠ Its `sections` branch is DEAD (measured: nothing renders it) — use get_page_layout / set_block_text for real page content.

  • get_page_layoutread-only

    One page's block tree, DRAFT-FIRST: the saved draft copy if there is one (`source` says which), otherwise the published document — block ids, order, enabled flags, editable fields.

  • reorder_blockswrite

    Reorders one page's blocks in the RETURNED overlay — the server saves nothing, and this is NOT the page's draft document.

  • set_block_enabledwrite

    Turns one block on or off in the RETURNED overlay — the server saves nothing, and this is NOT the page's draft document.

  • set_block_textwrite

    Sets bounded text overrides on one block, for one locale, in the RETURNED overlay — the server saves nothing, and this is NOT the page's draft document.

  • set_block_imagewrite

    Replaces or places a content image in one PAGE block's image slot, writing the page's DRAFT copy — a visitor keeps seeing the published picture until the draft is published (from the UI, or with publish_page_draft after the editor's explicit yes).

  • set_block_linkwrite

    Sets or clears the link target (`cel`) of one card or button — an internal page, an anchor on the page, or an external https URL — writing the page's DRAFT copy. The link only works once the target page is published.

  • set_block_embedwrite

    Sets the provider (YouTube, LinkedIn, Facebook, Google Maps) and URL of one embed block — the URL checked against the provider BEFORE writing — into the page's DRAFT copy. Nothing loads for a visitor before they click.

  • set_block_settingwrite

    Sets one block SETTING (justify, layout, picture size, hiding an icon, the divider line…) from the block-settings registry — written on the base-language page and copied to the other languages' drafts in the same commit; into the pages' DRAFT copies.

  • set_page_metawrite

    Writes a page's own meta (page image, short title, short description) — what a card pointing at the page shows, and the share image; not shown on the page itself. Writes the page's DRAFT copy.

  • list_imagesread-only

    The IMAGE LIBRARY: every stored content image once (page blocks, page image, share image, menu items, articles; published and draft, every language) — size, alt texts, where it is used; filter by text, shape, width and 'unused on live pages'. Returns the `/api/assets/…` URL to reuse.

  • get_editor_rulesread-only

    The editor rule lists (watched client names, client names cleared for publication, banned phrasings) — read BEFORE writing text; the server checks every text write against them.

  • propose_rule_changewrite

    Adds or removes entries in one rule list, TWO-PHASE: without `tervAzonosito` it returns a plan and writes nothing; after the editor's yes, the same id applies it. Audited with who and when.

  • bulk_editwrite

    BULK editing: rewrites every match of one filter (template · path · block type · field) in ONE store commit, into the DRAFT layer. With a MANDATORY plan phase: without a plan id the call only returns a PLAN and writes nothing.

  • list_articlesread-only

    Every Insights article's metadata, without bodies.

  • get_articleread-only

    One Insights article by slug, with its full body.

  • get_placement_suggestionread-only

    The deterministic placement suggestion for one article.

  • audit_ai_readinessread-only

    A 0-100 structural score, a per-check list and findings with block ids.

  • audit_social_readinessread-only

    An article's OR a page's social readiness: first the robots gate (0015), then a 0-100 score, the per-platform link cards, UTM share links and DRAFT post texts. For a page the served and the draft card apart. Posts nothing.

  • create_social_postwrite

    Stores a LinkedIn, Instagram or Facebook post DRAFT (platform, language, target page or article, text, hashtags); the link and the served link card come from the target, the Instagram image from its share image. Posts nothing.

  • update_social_postwrite

    Changes a post's text, hashtags or target; an approved post goes back to draft.

  • get_social_postwrite

    One post with its current preview; if the target's card changed since approval it puts the post back to draft (hence a writer).

  • list_social_postsread-only

    The posts (filtered by status, language and platform, discarded ones hidden by default), with previews. Read-only: shows a card change, does not write it.

  • set_social_post_imagewrite

    Sets an Instagram post's image: the target's share image or an uploaded one, at 4:5 or 1:1; an approved post goes back to draft. Posts nothing.

  • discard_social_postwrite

    Discards a post (`elvetett`): it leaves the default list and can not be approved.

  • approve_social_postwrite

    Approves a post TWO-PHASE: without `tervAzonosito` it returns a plan; after the editor's yes the same id applies it. Needs the publish right; the machine token can not approve. Posts nothing.

  • create_campaignwrite

    Creates a mini campaign: key (= utm_campaign), title, languages. Never overwrites a taken key. Posts and publishes nothing.

  • update_campaignwrite

    Changes a campaign's title or languages; a language is dropped only when no member post is in it.

  • get_campaignread-only

    Where a campaign stands: the landing per language (draft/published, card and findings), the member posts with status and link, studioUrl.

  • list_campaignsread-only

    The campaigns with landing status and member posts.

  • create_campaign_landingwrite

    Creates the campaign landing as a DRAFT from the campaign template at kampany/<key>, in every campaign language with its copy, no menu entry. Publishes nothing.

  • attach_post_to_campaignwrite

    Puts a post into a campaign: its link's utm_campaign becomes the campaign key; an approved post goes back to draft.

  • detach_post_from_campaignwrite

    Takes a post out of its campaign (the target-derived utm_campaign returns); a post on the draft landing can not leave.

  • audit_linksread-only

    Broken internal links per language as they render (menu, frame, blocks, articles), with a reason code; on request one scope's external URLs too. In draft mode it audits your own draft.

  • get_site_structureread-only

    The megamenu tree, the existing pages, the articles and the measured drift.

  • create_pagewrite

    Creates a NEW page by cloning an existing one's STRUCTURE (layout family, allowed blocks, block tree) and links it into the megamenu under a named — or path-inferred — parent. The page is NOT live (publishAt: null) and has no separate draft copy. Does not publish by itself — publish_page does, after the editor's explicit yes.

  • create_page_templatewrite

    Creates a NEW page TEMPLATE from an existing page's composition — dropping, reordering or adding blocks — and writes every language document in ONE commit. The page is NOT live (publishAt: null). It never improvises: a missing block type is named, not substituted.

  • validate_articleread-only

    The editorial rule verdict (PASS/FAIL), with a per-type rule set.

  • create_articlewrite

    Creates a NEW draft article; nothing here can publish it.

  • create_article_language_variantwrite

    Creates the EN/DE version of an existing article as a draft; nothing here can publish it.

  • update_articlewrite

    Writes a DRAFT article's title/summary/body and its public author (szerzo/szerep).

  • read_blockread-only

    The article's blocks with stable ids — the read to do before an edit.

  • write_blockwrite

    Replaces ONE block's text by id; every other block stays byte-identical.

  • generate_article_coverwrite

    Draws a 1200x630 branded cover on the server and inserts it into the draft.

  • create_document_uploadwrite

    A short-lived upload ticket for a certificate PDF.

  • set_block_documentwrite

    Puts a stored PDF into ONE document row of a certificates block — into every language's DRAFT that has the row, in one commit.

  • create_image_uploadwrite

    A short-lived upload ticket for a local image file.

  • add_article_imagewrite

    Inserts an image into the draft body from a URL, a site path or base64.

  • publish_pagewrite

    Makes pages visible to visitors (plan, chat confirmation, then apply). Does NOT publish a saved draft.

  • unpublish_pagewrite

    Withdraws pages: visitors get a 404, signed-in editors still see them. The draft is untouched.

  • publish_page_draftwrite

    Moves the pages' SAVED draft into the published document, every language in one commit; the plan carries the change list.

  • delete_pagewrite

    Deletes pages for good: every language's document and draft plus the menu entries pointing at them, in one commit. Explicit path list only.

  • move_pagewrite

    Moves a page to a new path: every language and draft, the menu entries and typed links in one commit; the old address answers 308 to the new one, no deploy.

  • create_language_variantwrite

    Creates a new language variant as a clone of the default-language page — born hidden, and never overwrites an existing translation.

  • edit_menuwrite

    Writes the menu with an operation list (insert, rename, move, remove), every affected language in one commit. Removing an entry does NOT delete the page.

  • edit_site_framewrite

    Writes the site frame with an operation list — footer items, group titles and a group title's target (the heading's link), contact values, the header CTA, the social links; every affected document in one commit, LIVE (the frame has no draft). A group cannot be added or removed.

  • get_integrationsread-only

    The site's INTEGRATIONS (CookieScript, HubSpot, GA4, GTM, Google Ads, Meta, Hotjar, LinkedIn, Google Maps): per kind its on/off state, the filled fields and the field descriptions — declared fields only.

  • set_integrationwrite

    Switches one integration on/off or writes its fields in two phases: a plan, then — after the publisher's yes — apply with the same plan id; LIVE, no deploy. Publishers only.

  • get_folder_manifestread-only

    The editor folder's file list (knowledge base + skill supplements) with hashes, the store version and a short-lived download ticket for the plugin's local sync — no file content.

  • propose_folder_changewrite

    Creates, changes or deletes editor-folder files in two phases: a plan, then — after the editor's yes — apply with the same plan id, in one commit.