Context7
Up-to-date docs for AI agents
제작자가 쓴 설명(영어 원문)
Research keywords, track rankings, audit sites, monitor backlinks and AI-search visibility — from…
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
MISARSEO_API_KEY, MISARSEO_BASE_URL, Authorization비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"misarseo": {
"command": "npx",
"args": [
"-y",
"@misarseo/mcp"
],
"env": {
"MISARSEO_API_KEY": "your-value",
"MISARSEO_BASE_URL": "your-value"
}
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add --transport http misarseo https://api.misar.io/seo/mcp --header 'Authorization: your-value'claude mcp add misarseo --env MISARSEO_API_KEY=your-value --env MISARSEO_BASE_URL=your-value -- npx -y @misarseo/mcp실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"misarseo": {
"url": "https://api.misar.io/seo/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"misarseo": {
"command": "npx",
"args": [
"-y",
"@misarseo/mcp"
],
"env": {
"MISARSEO_API_KEY": "your-value",
"MISARSEO_BASE_URL": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"misarseo": {
"type": "http",
"url": "https://api.misar.io/seo/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"misarseo": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@misarseo/mcp"
],
"env": {
"MISARSEO_API_KEY": "your-value",
"MISARSEO_BASE_URL": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
MISARSEO_BASE_URL envAuthorization 비밀 필수 HTTP header이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 GitHub 계정 Misar-AI 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: MISARSEO_API_KEY, Authorization
둘 다 가능해요. 내 컴퓨터에 설치해도 되고, 클라우드 버전에 연결해도 돼요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.0.0)은 21일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Context7, Codebase Memory, Exa
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Research keywords, track rankings, audit sites, monitor backlinks and AI-search visibility — from any AI assistant.
180 tools · 6 prompts · 3 resources · 6 agent skills
Works with Claude (Desktop, Code, and web), Cursor, VS Code, Windsurf, Cline, Zed, Gemini CLI, ChatGPT, and any other MCP-compatible client — over stdio or Streamable HTTP.
npx -y @smithery/cli install misar/misarseo-mcp --client claude
claude mcp add misarseo -- npx -y @misarseo/mcp@latest
{
"mcpServers": { "misarseo": { "command": "npx", "args": ["-y", "@misarseo/mcp@latest"], "env": { "MISARSEO_API_KEY": "mseo_your_key_here" } } } }
Ready-made configs for every client live in connectors/.
{
"mcpServers": { "misarseo": { "type": "streamable-http", "url": "https://api.misar.io/seo/mcp", "headers": { "Authorization": "Bearer mseo_your_key_here" } } } }
Create an API key at https://seo.misar.io/ai (AI & MCP → create an API key) — it starts with mseo_ — and give it to the server in one of three ways: the MISARSEO_API_KEY environment variable, your MCP client's env block, or { "api_key": "mseo_…" } in ~/.misarseo/config.json.
Self-hosted instances: set MISARSEO_BASE_URL.
| Tool | Description |
|---|---|
list_projects | Lists the active projects in the user's organization. |
get_dashboard | One card per active project in the caller's organization: latest audit health, rank-tracker status, and trailing-7-day web-analytics sessions. |
research_keywords | Research keyword data (search volume, difficulty, CPC, related ideas) for 1-5 seed keywords in one call — one research run per seed. |
save_keywords | Save keywords to a project's saved-keywords list. |
list_saved_keywords | Lists keywords saved to a project, with whatever metrics have been cached for them (search volume, difficulty, CPC) and their tags. |
classify_keyword_intent | Classify 1-200 keywords' search intent from their wording: informational, navigational, commercial, transactional, or unknown. |
get_keyword_potential | Parent Topic and Traffic Potential for one keyword, built from real SERP overlap across a BOUNDED set (up to 5) of related keywords — not a full keyword-to-URL reverse index, which this codebase's free stack does not have. |
get_keyword_serp_overview | Per-keyword SERP overview: a fresh live SERP snapshot for the keyword, PLUS — when this exact keyword happens to already be tracked in this project's rank tracking — its historical position trend and SERP volatility, read straight from the SAME rank-tracking services (get_rank_keyword_history/get_rank_volatility_index) already use. |
get_keyword_strategy | Keyword Strategy Builder: a volume -> cluster -> page -> brief pipeline over 1-500 pasted keywords, composed entirely from existing pieces — the same bulk keyword lookup, the same shared-phrase clustering engine the saved-keyword Topic Clusters feature and get_topic_research both already use, a text-match against the project's own crawled pages, and a BOUNDED number of AI-gateway content-brief calls (one per cluster among the top few by measured volume, gated by the shared AI-gateway budget). |
get_topic_research | Content ideas for a seed keyword, composed from three sources this codebase already fetches for other features: the SERP for the seed (titles of pages already ranking for it), PAA-style questions (real autocomplete completions reframed as questions), and autocomplete keyword suggestions. |
get_keyword_list_share_of_voice | Share of Voice across a saved keyword list: the project's own domain plus up to 3 competitor domains, scored over a saved-keyword tag ("a saved keyword list" in this codebase IS a saved-keyword tag — omit tagId/tagName to mean every saved keyword in the project). |
get_domain_overview | Returns a high-level view of a domain's organic footprint: estimated organic traffic, organic keyword count, and a 0-100 domain authority score. |
get_domain_batch | Domain batch analysis: one authority row per domain, up to 100 at once. |
get_domain_authority_history | Domain-authority history: the stored trend of dated authority snapshots for one project+domain, oldest first. |
capture_domain_authority_snapshot | Capture a domain-authority snapshot now: calls the same free resolver get_domain_overview already uses and records today's reading, so get_domain_authority_history has a trend to read back. |
find_serp_competitors | Compares domains competing in search results for a supplied keyword set. |
get_keyword_gap | Compares the project's own domain against up to 3 competitor domains and classifies every keyword a competitor ranks for as missing / behind / tied / ahead / unknown. |
list_competitor_monitors | Competitor page change detection: the specific competitor URLs monitored for a project, with lastCheckedAt (null until the first scheduled check reaches it). |
add_competitor_monitor | Start monitoring one competitor page for changes: title/meta, a real line-level content diff (added/removed/unchanged line counts — never a fabricated similarity score), outbound links, and structured-data types. |
remove_competitor_monitor | Stops monitoring one competitor URL. |
get_competitor_monitor_changes | Timeline of DETECTED changes for one monitored competitor URL, newest first — a check that found nothing does not appear here. |
get_rank_tracker | Read-only access to rank tracker configs and their latest results. |
add_rank_tracking_keywords | Adds keywords to an existing rank tracker config. |
get_rank_config_trend | Per-run keyword-position-distribution buckets for a tracker, oldest first — how many tracked keywords sit in the top 3, 4-10, 11-20, or outside the top 20, per check run. |
get_rank_movers | Newcomers and fast climbers for a tracker's OWN domain, over a window. |
get_rank_keyword_history | Per-keyword position series over time, oldest first — the same series the app's SERP-history chart draws for one tracked keyword. |
get_rank_volatility_index | SERP volatility index across recent runs — how much this tracker's own positions churned run over run, derived entirely from already-stored history (no new SERP calls). |
get_rank_ai_overview_trend | AI Overview presence trend across a tracker's keywords, oldest first — what share of tracked keywords showed Google's AI Overview in the SERP, per check run, and how that has moved over time. |
list_rank_annotations | Chart notes on a rank tracker's own timeline — 'deployed new title tags', 'algorithm update' — oldest first. |
add_rank_annotation | Adds a chart note to a rank tracker's own timeline. |
remove_rank_annotation | Removes a chart note from a rank tracker's own timeline. |
list_rank_cannibalisation | Tracked keywords whose latest ranking URL is not the target URL you declared for them (see set_rank_keyword_target_url). |
set_rank_keyword_target_url | Sets or clears the URL you intend to rank for a tracked keyword. |
list_rank_keyword_tags | Lists the tags in use on one rank tracker, plus the project's whole tag vocabulary. |
update_rank_keyword_tag | Attaches or detaches ONE tag across a selection of tracked keywords (up to 500 keyword IDs per call). |
get_brave_search_rank_check | Checks where a project's domain (or an explicit targetDomain) ranks in REAL Brave Search results for one keyword. |
create_rank_tracker | Creates a rank tracker config (domain + market + devices + schedule) for a project and returns its configId. |
list_rank_tracking_keywords | Lists the keywords tracked by ONE rank tracker: { keywords, totalCount, page, pageSize }, each row { id, configId, keyword, searchVolume, keywordDifficulty, cpc, metricsFetchedAt, createdAt }. |
remove_rank_tracking_keywords | Removes keywords from a rank tracker by their tracking-keyword IDs (from list_rank_tracking_keywords). |
start_site_audit | Starts a MisarSEO site crawl/audit from startUrl. |
get_site_audit_status | Progress of a site audit started by start_site_audit: { status, pagesCrawled, pagesTotal, lighthouseTotal, lighthouseCompleted, lighthouseFailed, currentPhase, startedAt, completedAt }. |
get_audit_comparison | Compare a site audit against an earlier one: which issues are new, which were fixed, how many persist, and the health-score delta. |
get_audit_core_web_vitals | Core Web Vitals report: LCP/INP/CLS per page/strategy this audit already ran Lighthouse against, classified against Google's own published thresholds. |
get_audit_https_report | HTTPS Report: percentage of pages secure, mixed-content and insecure-link counts, homepage HTTPS-path status, and HTTP URLs in an HTTPS site's sitemap — for a project's latest completed crawl (or a named earlier one). |
get_audit_internal_links | Internal Link Report: outbound/inbound internal link counts per page, orphan pages, dead ends, and click-depth distribution for a project's latest completed crawl (or a named earlier one). |
get_audit_structured_data | Structured Data Report: pages grouped by schema.org @type, which pages have none, and which pages carry an unparseable JSON-LD block — for a project's latest completed crawl (or a named earlier one). |
get_search_console_performance | Query the connected Search Console property's Search Analytics: clicks, impressions, CTR, and average position by query/page/country/device/date. |
inspect_urls | Run Google Search Console's URL Inspection on up to 10 URLs of the connected property: index/coverage state, last crawl time, Google-selected vs declared canonical, and mobile/rich-results verdicts. |
get_search_console_coverage | MisarSEO's own index-coverage report for the connected property: which URLs are indexed, excluded, or errored, and why. |
get_search_console_hourly_performance | MisarSEO's own retained HOURLY Search Console totals for the connected property — the hourly counterpart to get_search_console_performance's daily archive. |
get_search_console_sitemaps | Search Console sitemaps.list/sitemaps.get: every sitemap submitted for the connected property and its processing status (pending, last downloaded, warning/error counts, per-content-type submitted counts), or one named sitemap. |
get_gsc_ctr_by_position | CTR by ranking position: the site's own historical Search Console clicks/impressions bucketed by position (1-3, 4-10, 11-20, 21+ — mirroring this codebase's existing rank-tracking position-distribution buckets), with the REAL clicks-weighted CTR this project achieved at each bucket. |
get_gsc_anonymous_queries | Anonymized-query estimate: Search Console omits some rare queries entirely from a query-dimensioned response to protect searcher privacy (Google's own documented behaviour, not this codebase's assumption). |
get_cannibalisation_report | Finds the queries where the project's connected Search Console property competes with itself: two or more of its own pages drawing impressions for the same query, splitting that query's clicks, click signals and ranking history across URLs. |
get_content_decay_report | Finds pages whose clicks declined by a meaningful amount between two adjacent windows, read entirely from MisarSEO's own archived Search Console history (the top-200-per-day per-page archive the nightly sync fills in). |
| `get_backli
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요