HelpCenter.io for agents

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

• 연결 방식: 클라우드에서 실행
• 전송 방식: Streamable HTTP
• 카테고리: 기타

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

필요한 것

• 클라우드에서 실행설치할 것 없음. 인터넷으로 연결돼요

어떤 앱을 쓰세요?

https://mcp.helpcenter.io/agent

claude mcp add --transport http agent https://mcp.helpcenter.io/agent

{
  "mcpServers": {
    "agent": {
      "url": "https://mcp.helpcenter.io/agent"
    }
  }
}

{
  "servers": {
    "agent": {
      "type": "http",
      "url": "https://mcp.helpcenter.io/agent"
    }
  }
}

https://mcp.helpcenter.io/agent

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 6일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

• helpcenter_create_help_center AI에게 내리는 지시처럼 보여요

  Create a new HelpCenter.io help center for the user, with no account and no sign-in: the first step of building or migrating a help center for someone who does not have HelpCenter.io yet. What it returns (also as structuredContent): site_id, subdomain, api_key, claim_url, expires

• helpcenter_request_migration AI에게 내리는 지시처럼 보여요

  File a migration request: HelpCenter.io moves one or more knowledge bases (up to 50) into HelpCenter.io for the user, within 24 hours. Needs no agent_key and no account. Use it when a knowledge base is too big to fill yourself (more than 500 articles), when helpcenter_create_help

• helpcenter_get_migration_request

  Follow a migration request with the request_id and status_token helpcenter_request_migration returned. Needs no agent_key. Returns (also as structuredContent): status — queued, in_progress, with_our_team, completed or declined; the request stays open, and its help centers refuse

• helpcenter_get_help_center

  Read the status of the help center you created: whether the user has claimed it, when it is deleted, how full it is, a fresh preview link, and what is left to set up. Call it after writing content, before giving the user the claim link, and whenever a tool answers capability_lock

• helpcenter_discard_help_center

  Delete the help center you created, with everything in it, and revoke its agent key. Irreversible. Only when the user asks for it, or when you created it by mistake (a wrong name or language). There is no need to clean up after handing over the claim link: an unclaimed help cente

• helpcenter_list_imports

  List the help center's imports, newest first (at most 50), each with its status, plan and progress. Includes an import the user set up in the dashboard, so you can follow and run a source they connected there (a private Zendesk help center, for example). It is also where the resu

• helpcenter_scan_import

  Read a public Zendesk Guide, Intercom, Document360, Help Scout Docs, Front Knowledge Base or HelpDocs help center and answer what importing it would bring: its categories, articles and languages, and where each language lands here. Imports nothing yet. The fastest way to fill the

• helpcenter_get_import

  Read one import: its plan, what is chosen, and how a run is going — progress (articles created, updated, conflicts with edits made here, images copied and failed), the imported articles waiting for review, and error once a run stops. limit says how much room an unclaimed help cen

• helpcenter_choose_import

  Choose which categories and languages an import brings, and whether articles arrive as drafts (the default) or as they are at the source. Starts nothing. While the help center is unclaimed, a choice that would take it past its 500 articles is refused (limit_reached) with the room

• helpcenter_run_import

  Start an import now, with what is chosen, or run a finished or failed one again. The run reads the source in the background: follow it with helpcenter_get_import until status is completed or failed. Running again updates the articles it brought before and never adds them twice; a

• helpcenter_cancel_import

  Cancel an import: it never runs again and stops syncing. Nothing it already brought in is deleted, and scanning its address again later picks up what it brought, so nothing arrives twice. A queued or running import cannot be cancelled (import_running): wait for the run to end. Ar

• helpcenter_get_import_redirect_map

  For every article and category an import brought in: the path its page had on the old help center ('from') and the path of the page that replaced it here ('to'), 200 a page, in exactly the shape helpcenter_bulk_create_redirects takes. Use it so the old help center's links keep wo

• helpcenter_list_redirects

  List the help center's redirects, newest first: each sends a path the help center would otherwise answer with its not-found page on to one of its pages, with a 301. Works once the user has claimed the help center, verified their email address and activated a plan; until then it a

• helpcenter_create_redirect

  Send an old path of the help center ('from') on to one of its pages ('to') with a 301, for as long as nothing else on the help center answers that path. A path that already has a redirect is re-pointed, never duplicated. Works once the user has claimed the help center, verified t

• helpcenter_bulk_create_redirects

  helpcenter_create_redirect for up to 200 redirects in one call, saved in order (a later one for the same 'from' wins). A page of helpcenter_get_import_redirect_map can be passed as it is. Works once the user has claimed the help center, verified their email address and activated

• helpcenter_delete_redirect

  Delete a redirect: its path goes back to the help center's not-found page. Works once the user has claimed the help center, verified their email address and activated a plan; until then it answers capability_locked with the user's next step (helpcenter_get_help_center shows it to

• helpcenter_get_custom_domain

  Read the help center's custom domain: the domain, the DNS record the user must add at their DNS provider, and where it stands on the way to live. Poll it while the user sets up DNS: status moves from pending_dns through verifying and issuing_certificate to live, usually within mi

• helpcenter_set_custom_domain

  Connect the help center to the user's own domain (e.g. help.example.com), as its Settings page does. Then give the user the DNS record from the result to add at their DNS provider; the certificate is requested once the record points here, and the domain goes live minutes later. F

• helpcenter_remove_custom_domain

  Disconnect the help center from its custom domain, as its Settings page does: the domain stops answering, and the help center stays on its helpcenter.io address. Only when the user asks for it. Works once the user has claimed the help center, verified their email address and acti

• helpcenter_search_articles

  Full-text search a HelpCenter.io help center's articles by query string, returning ranked matches. This performs keyword search (Meilisearch-backed) over published article titles and content for the connected help center. Use it to answer "find the article about X" intents. It is

• helpcenter_list_articles

  List and browse a HelpCenter.io help center's articles, optionally filtered by category, status or last update, and ordered by views. Use this to browse "what's in category Y" or "the most-viewed articles", or to walk every article for an audit, a backup or an incremental sync, r

• helpcenter_create_article

  Create a new article in the connected HelpCenter.io help center. Requires a write-scoped API key (read-scoped keys get a permission error). Titles, content, and slugs are per-language objects keyed by language code. Slugs auto-generate from the title when omitted. Args: - title (

• helpcenter_update_article

  Update an existing article by id in the connected HelpCenter.io help center. Partial update: only the fields you pass are changed. Requires a write-scoped API key. Per-language fields (title, content, slug) are objects keyed by language code and merge per language. Args: - articl

• helpcenter_get_article

  Read one article by id from the connected HelpCenter.io help center. Use this when you already know the id — after a search, or before editing — instead of paging through helpcenter_list_articles to find it again. Read-only. Also the way to check whether an article has unpublishe

• helpcenter_bulk_create_articles

  Create or upsert many articles in one request. Use this for imports and migrations instead of calling helpcenter_create_article in a loop. Send at most 50 articles per call; split a larger import into batches of 50. Requires a write-scoped API key. Give every item an external_id:

• helpcenter_get_staged_changes

  Read the unpublished staged edits waiting on an article. Staged changes let you edit a PUBLISHED article without readers seeing it, then release it deliberately. Staged content is invisible to everything public: the rendered help center, sitemap, site search, the widget, the AI a

• helpcenter_stage_article_changes

  Save an edit to a published article WITHOUT readers seeing it. Nothing goes live until you call helpcenter_publish_staged_changes. Staged changes let you edit a PUBLISHED article without readers seeing it, then release it deliberately. Staged content is invisible to everything pu

• helpcenter_publish_staged_changes

  Apply staged changes to the live article, making them visible to readers. Staged changes let you edit a PUBLISHED article without readers seeing it, then release it deliberately. Staged content is invisible to everything public: the rendered help center, sitemap, site search, the

• helpcenter_discard_staged_changes

  Throw away staged edits without publishing them. The live article is untouched. Staged changes let you edit a PUBLISHED article without readers seeing it, then release it deliberately. Staged content is invisible to everything public: the rendered help center, sitemap, site searc

• helpcenter_list_article_versions

  List the archived previous versions of an article, so a past wording can be restored. Every publish archives the version it replaced. Read-only. Args: - article_id (number, required). - response_format ('markdown' | 'json'): default 'markdown'. Returns: { status: "success", versi

• helpcenter_restore_article_version

  Roll a live article back to a previously published version. Takes a version id from helpcenter_list_article_versions. The restore is itself archived, so it can be rolled forward again — this is reversible, but it DOES change what readers see immediately. Args: - article_id (numbe

• helpcenter_list_categories

  List the categories of the connected HelpCenter.io help center. Read-only. Returns each category's per-language name and description, parent id (for hierarchy), and icon. Use this to discover valid category ids before creating or filing articles, or to render the help center's st

• helpcenter_update_category

  Update an existing category by id in the connected HelpCenter.io help center. Partial update — only fields you pass change. Requires a write-scoped API key. Name and description are per-language objects keyed by language code. Args: - category_id (number, required): id of the cat

• helpcenter_create_category

  Create a category in the HelpCenter.io help center bound to your API key. Requires a write-scoped API key. This is what lets you build a help center's structure rather than only fill it in: create the categories first, then file articles into them with helpcenter_create_article's

• helpcenter_delete_category

  Delete a category from the HelpCenter.io help center bound to your API key. DESTRUCTIVE. The category is removed and its contents are moved somewhere else. Fails closed by default: a category holding articles or sub-categories answers 409 unless you say explicitly where its conte

• helpcenter_reorder_categories

  Set the order of categories in the HelpCenter.io help center bound to your API key, in one call. Requires a write-scoped API key. Prefer this over repeated helpcenter_update_category calls: an information architecture is decided all at once, and one call leaves no visibly half-so

• helpcenter_reorder_category_articles

  Set the reading order of the articles inside one category. Requires a write-scoped API key. Args: - category_id (number, required): the category whose articles are being ordered. - articles (array, required): the articles in the order you want them, as [{ id }] or [{ id, position

• helpcenter_get_template_guide

  Learn what can be customized in a help center's design and exactly how: the model, every edit operation with an example, every component with the settings and values it accepts, theme tokens, custom CSS rules and hooks, scripts and navigation. A help center's design is its v2 tem

• helpcenter_get_template

  Read a help center's current design (the draft): its status, the Template Editor link for the customer to review, and an outline of every page — or one part of the draft in full. A help center's design is its v2 template: theme tokens (colours for light and dark mode, fonts, radi

• helpcenter_list_template_themes

  List the ready-made themes a help center can start from, or describe one in full. A help center's design is its v2 template: theme tokens (colours for light and dark mode, fonts, radius, density), six page kinds (home, category, article, search, contact, notFound), each built fro

• helpcenter_apply_template_theme

  Start the draft from a ready-made theme — the Template Editor's "Compare & apply": copy all of a theme, or only some of its sections, onto the draft. A help center's design is its v2 template: theme tokens (colours for light and dark mode, fonts, radius, density), six page kinds

• helpcenter_update_template_settings

  Change document-level design settings in the draft: theme colours (light and dark), fonts, corner radius and density; the brand (name, logo, favicon); meta and SEO; and per-page settings such as a page's layout or how a category page lists its articles. It edits the help center's

• helpcenter_add_template_components

  Add components to pages of the draft: a Hero, a CategoryGrid, FeaturedArticles, Faqs, RichText, a CustomHtml block, a Container… It edits the help center's design DRAFT (its v2 template): the draft the dashboard's Template Editor opens, with a live preview. Nothing reaches visito

• helpcenter_update_template_components

  Change the settings of components already in the draft: a heading, a variant, a column count, a CustomHtml block's markup. It edits the help center's design DRAFT (its v2 template): the draft the dashboard's Template Editor opens, with a live preview. Nothing reaches visitors unt

• helpcenter_move_template_components

  Reorder or move components within their page: to another position among their siblings, to another region, into a Hero or Container, or out to the region's top level. It edits the help center's design DRAFT (its v2 template): the draft the dashboard's Template Editor opens, with

• helpcenter_remove_template_components

  Remove components from the draft, with everything nested inside them. It edits the help center's design DRAFT (its v2 template): the draft the dashboard's Template Editor opens, with a live preview. Nothing reaches visitors until helpcenter_publish_template — after editing, give

• helpcenter_update_template_region

  Style one region's wrapper on one page: its background, padding, bottom border and alignment. It edits the help center's design DRAFT (its v2 template): the draft the dashboard's Template Editor opens, with a live preview. Nothing reaches visitors until helpcenter_publish_templat

• helpcenter_sync_template_region

  Make a region one shared copy on every page, or let each page keep its own. It edits the help center's design DRAFT (its v2 template): the draft the dashboard's Template Editor opens, with a live preview. Nothing reaches visitors until helpcenter_publish_template — after editing,

• helpcenter_copy_template_region

  Copy one page's version of an unsynced region onto other pages, once, translations included. Each target page's region is replaced, and the pages stay independent afterwards; to keep them identical, sync the region with helpcenter_sync_template_region instead. It edits the help c

• helpcenter_add_template_css

  Add a labelled block of custom CSS to the design, to restyle components, regions or the whole help center beyond what the settings offer. It edits the help center's design DRAFT (its v2 template): the draft the dashboard's Template Editor opens, with a live preview. Nothing reach

• helpcenter_update_template_css

  Change one custom CSS block: replace its CSS, rename it, switch it on or off, or move it in the order. Fields left out keep their value. It edits the help center's design DRAFT (its v2 template): the draft the dashboard's Template Editor opens, with a live preview. Nothing reache

• helpcenter_remove_template_css

  Delete one custom CSS block from the draft. To see the design without it first, switch it off with helpcenter_update_template_css (enabled:false) instead. It edits the help center's design DRAFT (its v2 template): the draft the dashboard's Template Editor opens, with a live previ

• helpcenter_add_template_script

  Add a script or snippet to the help center's pages: an external script (src), inline JavaScript (inlineBody), or raw HTML such as a vendor snippet or a verification tag (htmlBody) — exactly one of the three — at the start or end of or , on every page kind or only some. It edits t

• helpcenter_update_template_script

  Change one script: its code (sending src, inlineBody or htmlBody switches it to that kind), position, pages, label or loading flags — or switch it off (enabled:false) without deleting it. Fields left out keep their value. It edits the help center's design DRAFT (its v2 template):

• helpcenter_remove_template_script

  Delete one script or snippet from the draft. To stop it running but keep it, switch it off with helpcenter_update_template_script (enabled:false) instead. It edits the help center's design DRAFT (its v2 template): the draft the dashboard's Template Editor opens, with a live previ

• helpcenter_set_template_navigation

  Replace the help center's navigation menu — the one every Navigation component draws, in the header or elsewhere — with the items given, in order. It edits the help center's design DRAFT (its v2 template): the draft the dashboard's Template Editor opens, with a live preview. Noth

• helpcenter_publish_template

  Put the draft live: every visitor sees the new design from now on. Records a version (restorable later) and starts a fresh draft from it — exactly the Template Editor's Publish button. A help center's design is its v2 template: theme tokens (colours for light and dark mode, fonts

• helpcenter_discard_template_changes

  Throw away every unpublished change in the draft and reset it to the live design. The live help center is not affected. Irreversible for the draft: edits that were never published cannot be recovered — including ones a person made in the Template Editor. Only discard when the cus

• helpcenter_list_template_versions

  List the help center's published design versions, newest first, marking the one that is live — with when, by whom and the publish note. Use it to find a version to bring back with helpcenter_restore_template_version. Args: - response_format ('markdown' | 'json'): default 'markdow

• helpcenter_restore_template_version

  Load an earlier published design into the DRAFT, replacing the draft's current content — to undo a change, or bring back a previous look. It does NOT go live until you publish it (unlike the Template Editor's one-click revert), so the customer can review it first. Unpublished dra

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검

• ! 주의

  제작자와 저장소 일치

  레지스트리에 소스 저장소가 없어서, 게시자(helpcenter.io)와 코드를 맞춰 볼 수 없어요

• … 아직 점검 안 함

  계속 관리되고 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• … 아직 점검 안 함

  라이선스 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  413ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✕ 실패

  도구 설명에 숨겨진 지시 없음

  도구 설명 2개에 AI에게 지시하는 것처럼 보이는 글이 있어요. 설치하기 전에 아래 내용을 읽어 보세요

기타 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 18349개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 18349개 중 90%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 18349개 중 24%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

제작자의 README

저장소에서 README를 찾지 못했어요