프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. 리뷰와 계정 기능은 다음 단계에서 열려요.
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

Howseen

제작자: howseen-ai버전 1.0.0i★ –i클라우드에서 실행
레지스트리 이름ai.howseen/howseen-mcp

설치

개요

제작자가 쓴 설명(영어 원문)

How ChatGPT, Gemini, Perplexity and Google AI name your brand, cite sources and rank rivals.

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

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

  • 연결 방식: 클라우드에서 실행
  • 전송 방식: Streamable HTTP
  • 카테고리: 마케팅 및 소셜 미디어
  • 입력해야 할 값: Authorization

설치

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

설치하기 전에

비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.

필요한 것

어떤 앱을 쓰세요?

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.

터미널에서 이 명령어를 실행하세요

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

실행하기 전에 빈 값을 채워 주세요.

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

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

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

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

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.

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

직접 입력할 값

  • 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월 8일 점검

  • ✓ 통과

    제작자와 저장소 일치

    레지스트리 이름이 도메인 howseen.ai 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)

  • … 아직 점검 안 함

    계속 관리되고 있음

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

  • … 아직 점검 안 함

    라이선스 있음

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

  • ✓ 통과

    엔드포인트 응답

    243ms 만에 응답(HTTP 200)

  • – 해당 없음

    OAuth로 로그인

    로그인 필요 없음

  • ✓ 통과

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

    도구 설명 44개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

마케팅 및 소셜 미디어 카테고리의 다른 서버와 비교i

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

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

자주 묻는 질문

Howseen, 안전한가요?

해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

입력해야 할 값: Authorization

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.0.0)은 19일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

대안

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

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

MCP YouTube Transcript

An MCP server retrieving transcripts of YouTube videos

제작자: jkawamoto성장 중★ 49511일 전 업데이트

내 컴퓨터에서 실행

Google Analytics MCP

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

제작자: surendranb성장 중↓ 1.1천/주★ 24411일 전 업데이트

내 컴퓨터에서 실행

BibiGPT YouTube Video Summarizer

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

제작자: JimmyLv성장 중★ 13711일 전 업데이트

클라우드에서 실행✓ bibigpt.co

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

Howseen MCP server

Ask Claude, ChatGPT, Cursor or Codex how your brand shows up in AI answers, and act on it, without leaving your AI assistant.

Howseen tracks which brands ChatGPT, Gemini, Perplexity, Google AI Overviews and Google AI Mode recommend on the questions your buyers ask, which sources those engines cite, and writes the content to win the spots you are missing. This repository documents its remote MCP server.

  • Server URL: https://app.howseen.ai/api/mcp (Streamable HTTP, remote, nothing to install)
  • Auth: Authorization: Bearer
  • Docs: https://howseen.ai/mcp
  • Get a key: Howseen dashboard > Settings > API & AI assistants (3-day free trial)

Connect your AI assistant

Replace hs_live_YOUR_KEY with your key.

Claude Code

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

Cursor (~/.cursor/mcp.json)

{

"mcpServers": { "howseen": { "url": "https://app.howseen.ai/api/mcp", "headers": { "Authorization": "Bearer hs_live_YOUR_KEY" } } } }

Codex

export HOWSEEN_API_KEY=hs_live_YOUR_KEY

codex mcp add howseen --url https://app.howseen.ai/api/mcp --bearer-token-env-var HOWSEEN_API_KEY

Claude.ai and ChatGPT (custom connector): these apps can only send the key inside the URL.

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

Treat that URL like a password: do not share it or show it on screen, and revoke the key in Settings if it leaks.

What you can ask

  • "What is my AI visibility this month, per engine?"
  • "On which buyer questions does ChatGPT name a competitor and not us?"
  • "Which sites does AI cite when we lose? Where should we get listed first?"
  • "What changed since the last scan?"
  • "Draft an article for the question we lose the most, then publish it to our site."

Tools

Read (any key)

ToolWhat it returns
list_brandsThe brands (websites) tracked in the account
get_visibility% of AI answers that name the brand, share of voice, average position, sentiment, per engine, with the trend
list_promptsTracked buyer questions with per-question visibility, engines and cited domains
get_competitorsBrand vs competitors in AI answers, overall and per engine
get_top_sourcesDomains and URLs AI engines cite most on the brand's questions
search_responsesReal AI answers, with excerpts, brands named and cited URLs
get_action_planPrioritized actions to raise AI visibility
get_prompt_gapsQuestions where AI names a competitor but not the brand
get_easiest_winsThird-party pages cited in the answers the brand loses, ranked
get_changesWhat changed between the last two scans
suggest_promptsBuyer questions worth tracking that are not tracked yet
list_articlesArticles Howseen wrote for the brand, with status and URL
get_article_performancePublished articles with indexing status, impressions and clicks
get_usagePlan, quotas used and left, API limits

Actions (key with actions enabled; every action previews first and only applies with confirm: true)

add_prompts, archive_prompts, remove_prompts, add_competitor, remove_competitor, mark_action_done, dismiss_action, draft_article, refresh_article, publish_article, request_indexing, create_share_report, delete_article, restore_article.

publish_article sends a written article to the brand's connected site (WordPress, Shopify, Ghost, BigCommerce, webhook) or its Howseen-hosted blog.

REST API

The same data is available as a read-only JSON API:

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

curl -H "Authorization: Bearer hs_live_YOUR_KEY" "https://app.howseen.ai/api/v1/brands/BRAND_ID/visibility?from=2026-09-01&engine=chatgpt"

Pricing

The MCP server and the API are included in the Pro plan (79 € a month) and the Business plans, and in the 3-day free trial. See https://howseen.ai/pricing.

Support

Questions or issues: open an issue here or write to raphael@howseen.ai.

PopNx에게 묻기