Howseen

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

• 接続方法: クラウドで動く
• トランスポート: Streamable HTTP
• カテゴリ: マーケティング・SNS
• 入力が必要なもの：Authorization

インストール

使っているAIアプリを選んで、設定をコピーしてください。

必要なもの

• クラウドで動くインストール不要。インターネット経由でつながります

どのアプリを使っていますか？

claude mcp add --transport http howseen https://app.howseen.ai/api/mcp --header 'Authorization: your-value'

{
  "mcpServers": {
    "howseen": {
      "url": "https://app.howseen.ai/api/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "servers": {
    "howseen": {
      "type": "http",
      "url": "https://app.howseen.ai/api/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。

自分で入力する値

• Authorization 秘密 必須 HTTP header
  Bearer token: your Howseen API key (Settings > API & AI assistants), as 'Bearer hs_live_...'

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

できること

ツールの名前と説明は、サーバーが2026年11月7日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。

• list_brands

  List the brands (websites) tracked in this Howseen account, with their id, name and domain. Call this first when the account may have several brands.

• get_visibility

  Headline AI visibility of a brand: % of AI answers that name it, share of voice vs competitors, average position, sentiment, per engine, plus the trend over the period (one point per scan).

• list_prompts

  The buyer questions (prompts) tracked for a brand, with per-prompt visibility, share of voice, position, which engines name the brand, and which brands and domains are cited.

• get_competitors

  Compare the brand with its competitors in AI answers: visibility %, share of voice, average position and sentiment, overall and per engine.

• get_top_sources

  The domains and URLs AI engines cite most when answering the brand's buyer questions, overall and per engine. Use it to find where the brand should get listed or mentioned.

• search_responses

  Read real AI answers collected for the brand: excerpts around the brand mention, whether the brand and which competitors were named, and the cited URLs. Filter by a word in the question or answer (query), by prompt text, and by engine.

• get_action_plan

  Prioritized actions to raise the brand's AI visibility (off-page: get listed on the pages AI cites; content: answer uncovered buyer questions; technical: site fixes, incl. links: = link a new article from 3 related pages, with copy-ready sentences in links.pages; setup: connectio

• list_articles

  Articles Howseen wrote for the brand (drafts, scheduled and published), with status, target question, GEO score and published URL.

• get_prompt_gaps

  Tracked prompts where AI names at least one competitor but not the brand, per engine, with the competitors named and the domains cited. Sorted by search volume (when a cached figure exists) then by number of competitors named. Start here to see what to win back.

• get_easiest_wins

  Third-party sites and pages cited in the answers the brand loses (competitor named, brand not), ranked by how many lost answers cite them, with the matching action-plan item. Getting listed there is the shortest path back into those answers.

• get_changes

  What changed between the last two completed scans (or since a date): prompts gained and lost, visibility delta per engine, tracked competitors newly named, and the likely causes (sources that started or stopped citing the brand).

• suggest_prompts

  Buyer questions worth tracking that the brand does not track yet: real questions from Hacker News discussions (ranked by engagement) plus AI suggestions for the category. Returns suggestions only; use add_prompts to track some. Limited to 20 calls per day.

• get_article_performance

  Articles written for the brand with status, GEO score, published URL and search-engine indexing status (Google URL Inspection, Bing), plus impressions and clicks when Search Console or Bing is connected.

• get_usage

  Plan, quotas used and left (prompts, competitors, articles, manual scans), next automatic scan estimate, what this API key may do, and the API rate limits. Call it before planning changes.

• get_next_action

  THE single most valuable next step for the brand, the same one the dashboard Overview shows (action engine, 20/80 ranking with the technical audit, Search Console and demand), with its steps, the questions it wins back and how to close it (which tool to call). Use it when the use

• get_site_audit

  Technical GEO/SEO audit of the brand's website, as the dashboard Technical audit shows it: every check (indexable, robots.txt, sitemap.xml, llms.txt, server rendering, Bing, structured data, canonical, trust signals), every issue with its severity and score gain, the steps for th

• get_content_plan

  The brand's content calendar with the real publication state of every article (planned, draft, scheduled, to publish by hand, failed, live on the brand's site), the Autopilot state, and the two answers to "what next?": next_to_write (a planned topic: write it with draft_article a

• get_connections

  The TRUE state of every connection of the brand, like Settings > Integrations: each publishing destination (CMS, own Next.js / API feed, hosted blog, webhook, copy-paste editor) with connected / needs_reconnect / copy_paste_only / waiting_for_site, whether articles can be publish

• get_search_console

  Google Search Console of the brand's own site: clicks, impressions, CTR, position, daily trend, top queries and pages, plus the opportunities Howseen derives (queries on page 2, low-CTR pages, queries Google shows an off-topic page for). Only the property covering this brand's si

• get_analytics

  GA4 traffic of the account's connected property: sessions, users, page views, daily trend, top sources and pages, plus the sessions and revenue AI assistants (ChatGPT, Perplexity, Gemini, Claude, Copilot...) send. For the AI part only, prefer get_ai_referrals. Not available with

• get_ai_referrals

  Real visits AI assistants send to the brand: GA4 sessions and revenue per assistant (ChatGPT, Perplexity, Gemini, Claude, Copilot...) and the pages they land on, an estimate of hidden AI visits (shown apart, never added), and the AI assistants that read the brand's Howseen-hosted

• get_sentiment

  How AI answers speak about the brand: % of the answers naming it that are positive (null under 3 answers), the positive / neutral / negative split with a real negative excerpt, per engine, compared with competitors, and the questions where the tone is negative.

• get_fanout_queries

  The web searches the AI engines ran behind each tracked question (latest scan): the queries to rank for so the AI finds the brand, overall and per question.

• get_brand_settings

  The brand profile (offer, category, language, markets, about, positioning, products), its competitors and its writing rules (the client's instructions, binding on every article), plus Autopilot. Read it before drafting or changing instructions.

• list_site_pages

  The brand's own website pages Howseen read when it joined (URL, title, summary): the inventory used for internal links, llms.txt and content refresh.

• get_pruning_review

  The quarterly content pruning review of the brand's website (the Action plan card "Quarterly pruning"): pages nobody finds in 90 days, pages that compete for the same Google queries (cannibalisation) and thin pages, each with ONE recommendation (improve with Content Refresh, merg

• mark_action_done

  Mark an action-plan item as done (same state as the dashboard Action plan). Use the action id from get_action_plan or get_easiest_wins. Preview first; confirm: true applies.

• dismiss_action

  Dismiss an action-plan item the user does not want to do (moves it to Archived in the dashboard, out of the next best actions). Reversible in the dashboard. Preview first; confirm: true applies.

• add_prompts

  Track new buyer questions (prompts) for the brand, checked against the plan's prompt quota (the whole list is refused if it would exceed it). An archived prompt added again is restored. Preview first; confirm: true applies.

• remove_prompts

  Stop tracking prompts and remove them from the prompt list (past scan results stay in history). Prefer archive_prompts to keep them listed. Preview first; confirm: true applies.

• archive_prompts

  Archive prompts: they stop being scanned (frees prompt quota) but keep their history and stay listed as archived in the dashboard, restorable. Preview first; confirm: true applies.

• add_competitor

  Track a competitor from a name or a website URL (resolved to name + domain like in Settings), within the competitor quota. Preview first; confirm: true applies.

• remove_competitor

  Stop tracking a competitor (by name or domain). Past results keep it. Preview first; confirm: true applies.

• draft_article

  Write a DRAFT article answering one buyer question, with the same quality pipeline as the app (brand context, the client's writing rules, sources AI cites, GEO checks). Never publishes. Give question (e.g. a prompt from get_prompt_gaps), or article_id of a planned topic of the co

• refresh_article

  Rewrite a WRITTEN article with the brand's current profile (offer, category, offerings, competitors) after it changed: same article id, slug, question and date, previous version kept (restorable in the app). A published article is never overwritten: the update lands in a refreshe

• create_share_report

  Create a public, frozen report link (visibility, competitors, top prompts, recommendations) with the account's agency branding, like the dashboard Share button. Preview first; confirm: true creates the link.

• run_scan

  Scan the brand's prompts on the AI engines now, with the same limit as the dashboard Run now button (a fresh scan at most once per brand per plan cadence: every 72h, every 24h on Business; prompts added since the last scan can be scanned alone; an unfinished scan can be continued

• update_brand_instructions

  Change the brand's writing instructions (Settings > Writing rules): the client's own rules every article must follow (tone, words to avoid, competitors never to name, facts to state...). Binding on every writing path from now on; an article breaking one is held, never published.

• set_autopilot

  Turn Autopilot on (articles of the content plan go live on the connected site on their date, once they meet the quality bar and the brand's rules) or off (nothing publishes automatically). Same switch as Howseen > Content. Preview first (says where it would publish); confirm: tru

• publish_article

  Publish a written article (e.g. a draft from draft_article) to the brand's connected CMS (WordPress, Shopify, Ghost, BigCommerce, GoHighLevel, Webflow, webhook) or hosted blog, now, or schedule it for a later date (needs Autopilot ON). Goes live publicly. Preview first; confirm:

• request_indexing

  Submit a published article to the search engines connected for the brand: Google (sitemap re-submit through Search Console when connected with indexing), Bing (Webmaster key) or IndexNow for pages hosted by Howseen. If you publish on your own site from the API or feed, pass url (

• apply_inbound_link

  Add the ready sentence that links one existing page of the brand's site to a newly published article (the links of a get_action_plan item whose id starts with links:), on the connected WordPress only. links.pages[].link_on says how: « existing_words » = the link is put on words a

• delete_article

  Move an article (planned, draft or published) to the Trash, like the dashboard delete button: restorable with restore_article or in Howseen > Content > Trash, and its topic is not planned again. A post already live on the client's own CMS (WordPress, Shopify...) is NOT removed fr

• restore_article

  Bring back an article from the Trash (e.g. one deleted with delete_article). Preview first; confirm: true restores.

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月10日にチェック

• ✓ 合格

  作者とリポジトリが一致

  レジストリ名はドメイン howseen.ai で確認済みです（レジストリがドメインの所有を確認しています）

• … 未チェック

  今もメンテナンスされている

  このリポジトリはまだGitHubから読み取っていません

• … 未チェック

  ライセンスがある

  このリポジトリはまだGitHubから読み取っていません

• ✓ 合格

  エンドポイントが応答する

  243ミリ秒で応答（HTTP 200）

• – 対象外

  OAuthでサインイン

  サインイン不要

• ✓ 合格

  ツールの説明に隠れた指示がない

  44件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした

マーケティング・SNSのほかのサーバーとの比較i

• このカテゴリのほかの3719件のうち0%よりスターが多い
• このカテゴリのほかの3719件のうち60%より最近レジストリに公開
• 基本チェックの結果が、このカテゴリのほかの3719件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方：↓ 週あたりのダウンロードi★ GitHubスターi3つの柱：レビュー · チェック · 利用状況i更新＝最新バージョンをレジストリに公開した日i

作者のREADME

claude mcp add --scope user --transport http howseen https://app.howseen.ai/api/mcp --header "Authorization: Bearer hs_live_YOUR_KEY"

{

export HOWSEEN_API_KEY=hs_live_YOUR_KEY

https://app.howseen.ai/api/mcp?key=hs_live_YOUR_KEY

curl -H "Authorization: Bearer hs_live_YOUR_KEY" https://app.howseen.ai/api/v1/brands