MCP Server
serpmantics
io.github.AmauryDvl/serpmantics
What this MCP does
Creates and manages SEO content guides, SERP analyses, search-intent and E-E-A-T audits, outlines, metadata, internal-linking suggestions, and brand voice briefs.
Capabilities
Tools
33
tools
create_citation_check
create_citation_check
Test whether ChatGPT, Perplexity and Google AI Overview cite a website for one question (free tool)
Asks one question to three AI answer engines (ChatGPT with web search, Perplexity, Google AI
Overview) in the chosen market, and reports for each engine whether your domain is cited as a
source (`cited`, a citation on your registrable domain or one of its subdomains), whether your
brand is named in the answer (`mentioned`, which is NOT a citation), which of your pages are cited,
an excerpt of the answer, its sources, and the domains cited instead of yours.
**One answer, on one day.** This is a snapshot, not a lasting measure: AI answers change from one week
to the next, and between two calls. Run the test again to compare.
**Asynchronous, poll the result.** This call only starts the test and answers HTTP 202 with a
`checkId` and a `pollUrl`. Call `GET /api/v1/tools/citation-check?checkId=...` every 3 seconds
until `status` is `done` or `failed`; a test usually takes less than 2 minutes. MCP clients must
call the `get_citation_check` tool again until the status is terminal.
**Identical questions are reused for 24 hours.** The same question (case and spaces ignored) in
the same market, asked less than 24 hours ago, returns the engine answers already collected,
recomputed for your domain: HTTP 200 with `reused` true and `status` already `done`. Nothing is
paid for again, and your daily quota is given back.
**Domain.** Send a domain name or any URL of the site: it is reduced to its registrable domain
(`https://www.example.co.uk/blog/` becomes `example.co.uk`). IP addresses, local names and unknown
suffixes return 400 INVALID_DOMAIN.
**Tiers, per UTC day.**
- Without an API key, free anonymous tier: 1 test per day per IP address.
- Signed-in account, or API key of an account whose plan includes API access: 10 tests per day.
The API key of an account whose plan does NOT include API access does not authenticate, and the
call returns 401. Remove the `Authorization` header to use the free anonymous tier instead.
Quota headers: `X-RateLimit-Limit`, `X-RateLimit-Used`, `X-RateLimit-Remaining`,
`X-RateLimit-Reset` (Unix time of the next UTC midnight). `Retry-After` is set on 429 and 503.
A 502 or 503 answer gives the consumed quota back, and so does a 429 FREE_CAPACITY_REACHED
and a 200 reused answer; SERVICE_UNAVAILABLE consumes none.
**Request format.** Send the body as JSON with `Content-Type: application/json`: any other
content type returns 415. Without an `Authorization` header, a request sent by a web page of
another site (an `Origin` other than the SERPmantics app, or `Sec-Fetch-Site: cross-site`)
returns 403. Server-to-server calls send no `Origin` header and are not affected.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['domain', 'question', 'market'], 'properties': {'domain': {'type': 'string', 'description': 'Domain to look for in the answers, or any URL of the site. Reduced to the registrable domain.'}, 'market': {'enum': ['fr-FR', 'en-US', 'es-ES', 'de-DE', 'it-IT'], 'type': 'string', 'description': 'Language and country in which the engines are asked.'}, 'question': {'type': 'string', 'description': 'The question a prospect would ask an AI assistant, 10 to 200 characters once spaces are collapsed.'}}}
create_eeat
create_eeat
Start an E-E-A-T analysis on a guide content
Starts an asynchronous E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) analysis
on the HTML content provided for a given guide. The analysis runs in the background — use
GET /api/v1/eeat to poll for results until `status` is `done` (or `failed`).
**Note:** This endpoint uses tokens (check /api/v1/tokens-usage for the cost, might vary).
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId', 'html_content'], 'properties': {'guideId': {'type': 'string', 'description': 'ID of the guide to analyze'}, 'html_content': {'type': 'string', 'description': 'HTML of the article to analyze (without `<mark>` tags)'}}}
create_eeat_competitors
create_eeat_competitors
Start an E-E-A-T analysis on a guide's top SERP competitors
Starts an asynchronous E-E-A-T analysis on the top competitors of the guide's SERP.
Each competitor is fetched and scored individually. Use GET /api/v1/eeat-competitors to
poll for results until `pending` reaches `0`.
**Token cost:** This endpoint charges `eeatCompetitorsTokensCostPerCompetitor`
(see /api/v1/tokens-usage) per competitor analyzed, up to 10 competitors.
Example: 10 competitors × 5 tokens = 50 tokens. 6 competitors × 5 tokens = 30 tokens.
The number of competitors corresponds to the deduplicated URLs in the guide's top-10 SERP
results (available via GET /api/v1/guide).
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId'], 'properties': {'guideId': {'type': 'string', 'description': 'ID of the guide whose competitors should be analyzed'}}}
create_guides
create_guides
Create new guides
Create one or more new guides based on provided queries.
Each guide targets exactly ONE engine and ONE analysis mode, chosen with the optional `source` field (default `google`).
How to request each guide type:
1. Google SERP guide (1 credit per guide): omit `source`, or pass `source: "google"`.
Example payload: {"queries": ["best crm"], "lang": "en-us"}
1bis. Google AI Overview guide (1 credit per guide). Two modes, like AI engines:
`source: "google_ai_overview"` builds the guide from the TEXT of Google's AI answers
(AI Overview, completed with AI Mode answers) ; `source: "google_ai_overview_citations"`
builds it from the content of the web SOURCES those answers cite (recommended for GEO).
Same language/country parameters as a Google SERP guide, 1 credit per guide in both modes.
Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "google_ai_overview_citations"}
2. LLM ANSWER guide (4 credits per guide): pass the engine name alone, e.g. `source: "chatgpt"`.
The guide is built from the answer text the AI generates for the query.
Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt"}
3. LLM CITATIONS guide (4 credits per guide) [RECOMMENDED AI mode]: pass the engine name with the `_citations` suffix, e.g. `source: "chatgpt_citations"`.
The guide is built from the content of the web pages the AI cites in its answer.
Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt_citations"}
Which AI mode to pick? For GEO (getting a page visible in AI answers), prefer `<engine>_citations`:
AI engines send traffic by CITING pages as sources, so the winning move is to look like the pages they cite.
The answer-text mode (`<engine>` alone) is mostly useful to analyze how the AI phrases its own answer.
When in doubt, pick `<engine>_citations`.
The same two modes exist for every AI engine (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek).
To optimize the same page for several engines or modes (e.g. Google AND ChatGPT answers AND ChatGPT sources), create one guide per source value on the same query.
IMPORTANT, HOW TO READ THE RESPONSE OF THIS ENDPOINT, WHICH SPENDS CREDITS.
Queries listed in `guidesFailed` are PROVEN not to have produced a guide and their credit was
given back (unless the account has unlimited credits, where nothing was reserved): re-sending
them is free and correct. Queries listed in `guidesUnknown` have an UNDECIDABLE outcome and
their credit is deliberately KEPT, because the guide was most likely written: DO NOT re-send
them, you would pay for the same guide twice. Look them up in `GET /api/v1/guides` after a few
minutes instead, and contact support if nothing shows up.
Finally, a `200` is NOT a promise that every query produced a guide: compare `guides.length`
with the number of queries you sent, never read `success` alone, and never re-send a query
just because it is missing from `guides`.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['queries', 'lang'], 'properties': {'lang': {'type': 'string', 'description': 'Language code for the guides'}, 'source': {'enum': ['google', 'google_ai_overview', 'google_ai_overview_citations', 'chatgpt', 'chatgpt_citations', 'perplexity', 'perplexity_citations', 'claude', 'claude_citations', 'gemini', 'gemini_citations', 'grok', 'grok_citations', 'mistral', 'mistral_citations', 'deepseek', 'deepseek_citations'], 'type': 'string', 'description': "Target engine AND analysis mode the guide optimizes for. One guide = one source. `google` analyzes the Google SERP (1 credit per guide). Google's AI answers have the same two modes as AI engines : `google_ai_overview` analyzes the TEXT of the AI answers (AI Overview, completed with AI Mode) ; `google_ai_overview_citations` analyzes the content of the web SOURCES those answers cite, the recommended mode for GEO. 1 credit per guide in both modes, same language/country parameters as `google`. For AI engines (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek), pick the mode: `<engine>` analyzes the AI's generated ANSWER for the query; `<engine>_citations` analyzes the content of the web SOURCES the AI cites, which is the recommended mode for GEO (become one of the cited sources). Both AI modes cost 4 credits per guide. Omit for the default `google`."}, 'queries': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Array of queries to create guides for'}}}
create_intent
create_intent
Generate search intent analysis for a guide
Analyzes search intent for a guide and optionally analyzes provided content against that intent.
**Note:** This endpoint uses tokens (check /api/v1/tokens-usage for the cost, might vary).
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId'], 'properties': {'content': {'type': 'string', 'description': 'Optional content to analyze against the intent (only after intent analysis was created)'}, 'guideId': {'type': 'string', 'description': 'ID of the guide'}}}
create_internal_links
create_internal_links
Generate internal linking suggestions for a guide
Analyzes a guide and generates internal linking suggestions based on content analysis.
**Note:** This endpoint uses tokens (check /api/v1/tokens-usage for the cost, might vary).
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId'], 'properties': {'guideId': {'type': 'string', 'description': 'ID of the guide'}}}
create_meta
create_meta
Generate SEO meta titles and descriptions for a guide
Generates optimized meta titles and descriptions based on guide content analysis.
**Note:** This endpoint uses tokens (check /api/v1/tokens-usage for the cost, might vary).
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId'], 'properties': {'guideId': {'type': 'string', 'description': 'ID of the guide'}}}
create_outline
create_outline
Generate content outline for a guide
Generates a content outline based on SERP analysis for a guide.
**Note:** This endpoint uses tokens (check /api/v1/tokens-usage for the cost, might vary).
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId'], 'properties': {'guideId': {'type': 'string', 'description': 'ID of the guide'}}}
create_persona_brief
create_persona_brief
Generate an AI persona and brand voice brief from the pages of a website (free tool)
Reads public pages of a website and produces an editorial persona and writing style brief:
who writes, for whom, tone on 6 axes, vocabulary, structure, do and don't lists, verified
quotes from the pages, style metrics measured on the text, and a ready-to-paste writing
prompt for any AI writing tool (`brief.writingPrompt`, plus `brief.writingPromptCompact`
of at most 1500 characters).
**Asynchronous, poll the result.** This call only starts the job and answers HTTP 202 with a
`briefId` and a `pollUrl`. Call `GET /api/v1/tools/persona-brief?briefId=...` every 3 seconds
until `status` is `done` or `failed`. A brief takes about 80 seconds plus 5 seconds per page,
rounded up to the half minute: about 2 min for 3 pages, 2 min 30 s for 10 pages.
MCP clients must call the `get_persona_brief` tool again until the status is terminal.
**Identical requests are reused for 72 hours.** The same set of URLs, in any order, with the
same `outputLanguage` and the same `brandName`, returns the brief already computed instead of
computing it again: HTTP 200 with `reused` true, `status` already `done`, the original
`briefId` and `reusedCreatedAt`, the date of the brief it reuses. Nothing is created, and your
daily quota is given back, so a reused answer costs you nothing. The pages of a reused brief
are listed in the order of the original request, not in the order you just sent. Send
`force` true to skip the lookup and compute a new brief, which answers 202 and consumes quota.
**Addresses.** Duplicate URLs, compared once normalized, are read once. A private, local or
blocked address is not refused by this call: the brief is created, and that page ends with
`status` failed and `failureReason` BLOCKED_ADDRESS (the brief fails with NO_USABLE_PAGE when
no other page could be read).
**Tiers, per UTC day.** Every tier is capped at 10 URLs per brief since 21 September 2026.
- Without an API key, free anonymous tier: 3 briefs per day per IP address, 10 URLs per brief.
- Signed-in account on the web interface, plan without API access: 10 briefs per day, 10 URLs per brief.
- API key of an account whose plan includes API access, pro tier: 50 briefs per day, 10 URLs per brief.
The API key of an account whose plan does NOT include API access does not authenticate, and the
call returns 401. Remove the `Authorization` header to use the free anonymous tier instead.
Quota headers: `X-RateLimit-Limit`, `X-RateLimit-Used`, `X-RateLimit-Remaining`,
`X-RateLimit-Reset` (Unix time of the next UTC midnight). `Retry-After` is set on 429 and 503.
A 502 or 503 answer gives the consumed quota back, and so does a 429 FREE_CAPACITY_REACHED
and a 200 reused answer; SERVICE_UNAVAILABLE consumes none.
**Request format.** Send the body as JSON with `Content-Type: application/json`: any other
content type returns 415. Without an `Authorization` header, a request sent by a web page of
another site (an `Origin` other than the SERPmantics app, or `Sec-Fetch-Site: cross-site`)
returns 403. Server-to-server calls send no `Origin` header and are not affected.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['urls'], 'properties': {'urls': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Public http(s) URLs of representative pages of one website, 5 to 10 articles give the best brief. At most 10 URLs, whatever the tier, each of at most 2048 characters.'}, 'force': {'type': 'boolean', 'description': 'True to compute a new brief even when an identical one exists, which answers 202 and consumes quota. Any value that is not a boolean returns 400 INVALID_BODY.'}, 'brandName': {'type': 'string', 'description': 'Optional brand name, on a single line, used in the brief.'}, 'outputLanguage': {'enum': ['fr', 'en', 'es', 'de', 'it'], 'type': 'string', 'description': 'Language in which the brief is written. When omitted, the service chooses it.'}}}
create_score
create_score
Analyze content optimization score
Analyzes the optimization score of the provided content for a specific guide
MCP channel defaults: this tool sends scoreProgressive=false, includeEmbedding=false when you leave them out. That is specific to this channel and overrides the default documented on those parameters, which describes the REST API. What it changes in the response: with scoreProgressive=false, contentAnalysis.progressiveScores comes back empty ({}); with includeEmbedding=false, contentAnalysis.embeddingAnalysis is omitted from the response. Set a flag to true in your arguments to get its content back; any value you do pass is sent unchanged, including false. The whole response is handed to the model, and this is where most of its size goes, so it is opt-in on this channel: ask only for what you are going to read.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId', 'content'], 'properties': {'content': {'type': 'string', 'description': 'Content to analyze'}, 'guideId': {'type': 'string', 'description': 'ID of the guide to analyze'}, 'pageUrl': {'type': 'string', 'description': "Optional. Read only for a visitor of a guide shared in read-only mode: the URL of one of the guide's SERP pages, whose stored content is then analysed instead of the guide's text. Ignored for the owner and for a guide shared in edit mode. Unknown URL: the guide's text is analysed.\n"}, 'saveToGuide': {'type': 'boolean', 'description': 'Whether to save the content and the analysis score back to the guide (default: true)\n'}, 'includeEmbedding': {'type': 'boolean', 'description': 'Whether to compute the semantic embedding analysis, i.e. proximity and PCA (default: true). When false, the embeddingAnalysis key is omitted from the response. Null is treated as "not provided", so the default applies.\n'}, 'scoreProgressive': {'type': 'boolean', 'description': 'Whether to compute the progressive score build-up curve (default: true). When false, progressiveScores is returned empty. Null is treated as "not provided", so the default applies.\n'}}}
delete_guide
delete_guide
Delete a guide
Deletes a specific guide. Deliberately NOT blocked by the 180-day expiry: an expired guide can no longer be read, but it can always be deleted, so that you can still clean up your account.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'The ID of the guide to delete'}}}
delete_guides
delete_guides
Delete multiple guides
Deletes multiple guides at once
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
delete_intent
delete_intent
Delete generated intent analysis for a guide
Removes previously generated intent analysis for the given guide.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId'], 'properties': {'guideId': {'type': 'string', 'description': 'ID of the guide'}}}
delete_internal_links
delete_internal_links
Delete generated internal-links suggestions for a guide
Removes previously generated internal-links suggestions for the given guide.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId'], 'properties': {'guideId': {'type': 'string', 'description': 'ID of the guide'}}}
delete_meta
delete_meta
Delete generated meta for a guide
Removes previously generated meta titles/descriptions for the given guide.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId'], 'properties': {'guideId': {'type': 'string', 'description': 'ID of the guide'}}}
delete_outline
delete_outline
Delete generated outline for a guide
Removes previously generated outline data for the given guide.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId'], 'properties': {'guideId': {'type': 'string', 'description': 'ID of the guide'}}}
discover_persona_brief_pages
discover_persona_brief_pages
Find the representative pages of a website from its sitemaps, before generating a persona brief (free tool)
Reads the sitemaps of a website (declared in robots.txt, otherwise /sitemap.xml,
/sitemap_index.xml and /wp-sitemap.xml) and returns up to 200 URLs of the same host, editorial
pages first. The first URLs, as many as the URL limit of your tier, are flagged `suggested`:
send them in `urls` to `POST /api/v1/tools/persona-brief`.
Same tiers as the creation call, with their own daily counter per UTC day: 20 discoveries per
day per IP address without an API key, 50 for a signed-in account, 200 with the API key of an
account whose plan includes API access. A key whose plan does not include API access returns
401: remove the `Authorization` header to use the free anonymous tier.
Quota headers: `X-RateLimit-Limit`, `X-RateLimit-Used`, `X-RateLimit-Remaining`,
`X-RateLimit-Reset`. `Retry-After` is set on 429 and 503. A 400, 502 or 503 answer gives the
consumed quota back; SERVICE_UNAVAILABLE consumes none.
**Request format.** Send the body as JSON with `Content-Type: application/json`: any other
content type returns 415. Without an `Authorization` header, a request sent by a web page of
another site (an `Origin` other than the SERPmantics app, or `Sec-Fetch-Site: cross-site`)
returns 403. Server-to-server calls send no `Origin` header and are not affected.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['site'], 'properties': {'site': {'type': 'string', 'description': 'URL or domain of the website. A bare domain is completed with https.'}}}
get_aissistant_tokens
get_aissistant_tokens
Get the current user's available AI tokens
Returns the number of AI tokens available to the authenticated user.
These tokens fund EVERY AI feature in SERPmantics — meta, outline,
intent, internal-links, EEAT, EEAT competitors, score, AND the
AISSistant prompts. The endpoint lives under /aissistant for
historical reasons but the balance is shared across all AI features.
Do NOT confuse with guide-creation credits (see /api/v1/credits).
For a combined view (credits + tokens) prefer /api/v1/credits.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
get_citation_check
get_citation_check
Read an AI citation test, poll until it is done
Returns the test started by `POST /api/v1/tools/citation-check`. While `status` is `pending` or
`running`, call again every 3 seconds: each engine fills in as soon as it has answered. When
`status` is `done`, at least one engine answered; `summary.citedBy` engines cite your domain out
of `summary.enginesAnswered` engines that answered. When `status` is `failed`, `failureCode` says
why (NO_ENGINE_ANSWERED, TIMEOUT, INTERNAL).
Per engine: `cited` is true when a source of the answer is on your registrable domain or one of
its subdomains, and `citedUrls` lists those pages; `mentioned` is true when your brand name appears
in the answer text, which is NOT a citation. `status` no_answer means the engine showed no answer
for this question (Google often shows no AI Overview), which is not a failure.
No quota is consumed. The `checkId` is random: whoever holds it can read the test, which is what
makes share links work. Tests expire after 30 days. Reads that are not attributed to an account are
capped at 1000 per IP address and per UTC day, far above any legitimate polling: crossing it returns
429 READ_RATE_LIMITED with `Retry-After`.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['checkId'], 'properties': {'checkId': {'type': 'string', 'description': 'The checkId returned by the creation call (22 characters).'}}}
get_credit_ledger
get_credit_ledger
Grand-livre crédits d'un compte (admin)
Timeline complète et immuable des mouvements de crédits d'un utilisateur (octrois, consommations, refunds, resets, ajustements admin), avec libellés FR en clair, delta signé, solde après, source, auteur et référence. Inclut le solde reconstruit à une date arbitraire (paramètre `at`) et un contrôle de cohérence (solde == dernier balanceAfter == somme des deltas). Réservé aux administrateurs. Lecture seule.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['userId'], 'properties': {'at': {'type': 'string', 'description': 'Date ISO pour reconstruire le solde à cet instant (point-in-time).'}, 'limit': {'type': 'number', 'description': 'Nombre maximum de lignes (défaut 200, max 1000).'}, 'userId': {'type': 'string', 'description': "Identifiant Mongo de l'utilisateur."}}}
get_credits
get_credits
Get user balance (guide credits + AI tokens)
Returns the authenticated user's full balance.
SERPmantics has TWO distinct currencies:
- **credits** (`credits`): how many NEW GUIDES the user can still create.
Consumed once per guide creation. `"unlimited"` if the user's plan
grants unlimited guide creation (`hasUnlimitedCredits: true`).
- **AI tokens** (`tokens`): pool consumed by every AI feature (meta,
outline, intent, internal-links, EEAT, EEAT competitors…).
Each feature has its own cost — call `/api/v1/tokens-usage` to get
the per-feature pricing.
Do not confuse the two: running out of `credits` blocks new guides;
running out of `tokens` blocks AI features inside existing guides.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
get_eeat
get_eeat
Get E-E-A-T analysis results
Retrieves the result of an E-E-A-T analysis.
`guideId` is **always required**: access is granted on the guide, so a request without it
is answered with `404 Guide not found`. `eeatId` is an optional filter on top of it: pass it
to fetch one specific analysis of that guide, omit it to fetch the latest one.
An `eeatId` that does not belong to `guideId` is answered with `404`, never with the
other account's data.
Poll this endpoint until `status` is `done` (results available) or `failed`.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId'], 'properties': {'eeatId': {'type': 'string', 'description': 'Optional filter, ID of one specific analysis of that guide (returned by POST /api/v1/eeat). Omit it to get the latest analysis of `guideId`.'}, 'guideId': {'type': 'string', 'description': 'ID of the guide the analysis belongs to. Required, and access is checked on it.'}}}
get_eeat_competitors
get_eeat_competitors
Get E-E-A-T analysis results for a guide's competitors
Retrieves the E-E-A-T analysis results for the top competitors of a guide.
Poll this endpoint until `pending` is `0` to know when the full analysis is complete.
Individual competitor results are available as soon as their `status` is `done`.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId'], 'properties': {'guideId': {'type': 'string', 'description': 'ID of the guide whose competitors should be returned'}}}
get_guide
get_guide
Get data for a specific guide
Retrieves details of a specific guide. While the guide is being created, the endpoint returns 202 (poll again later). If the creation failed permanently (explicit terminal flag, or a failure older than 15 minutes with no retry left, see progressStatus.terminalInferred), it returns 200 with success=false, status=failed, a human-readable French error message, creationFailed=true, refunded (whether the consumed credits were automatically given back) and guide.progressStatus (raw reason, message, terminal). Stop polling in that case.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'The ID of the guide to retrieve'}}}
get_guides
get_guides
List user's guides
Returns a list of guides for the authenticated user.
Use `query` to check whether a guide already exists before creating one
(creating a duplicate costs credits). Beware of two behaviours of this endpoint:
- `query` and `group` are case-insensitive REGULAR EXPRESSIONS, not exact matches:
special characters in the value are interpreted as regex syntax, and an invalid
regex returns no result at all. (`status` is different: a known status is matched
exactly, any other value falls back to a regex.) Always compare the returned
`query` and `source` yourself, and fall back to an unfiltered paginated scan
before concluding that nothing exists;
- `totalCount` does NOT take `query` nor `group` into account (known limitation:
both are applied as application-level regexes that the count query does not
know, so it returns 0 as soon as either is used, alone or combined with
`status`). Filtering on `status` alone does give a correct `totalCount`, since
it is a real stored field. For an existence check, trust the `guides` actually
returned; `totalCount` is only reliable for paginating a listing filtered by
`status` alone, or not filtered at all.
An empty result is returned as a 404 with `success: false` and
`error: "No guides returned"`, not as an empty list.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'page': {'description': 'Page number for pagination'}, 'group': {'type': 'string', 'description': 'Filter on the guide group. Case-insensitive partial match, interpreted as a regular expression.'}, 'query': {'type': 'string', 'description': 'Filter on the guide query. Case-insensitive partial match, interpreted as a regular expression (see the endpoint description).'}, 'status': {'enum': ['draft', 'active', 'review', 'published', 'archived'], 'type': 'string', 'description': 'Filter on the guide status. Exact match when the value is one of the known statuses, otherwise a case-insensitive regular expression.'}, 'pageSize': {'description': 'Number of guides per page'}}}
get_intent
get_intent
Get search intent analysis for a guide
Retrieves existing intent analysis results for a guide
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId'], 'properties': {'guideId': {'type': 'string', 'description': 'ID of the guide'}}}
get_internal_links
get_internal_links
Get internal linking suggestions for a guide
Retrieves existing internal linking suggestions for a guide
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId'], 'properties': {'guideId': {'type': 'string', 'description': 'ID of the guide'}}}
get_meta
get_meta
Get generated meta titles and descriptions for a guide
Retrieves generated SEO meta titles and descriptions for a guide
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId'], 'properties': {'guideId': {'type': 'string', 'description': 'ID of the guide'}}}
get_outline
get_outline
Get generated page structure for a guide
Retrieves the generated page structure (flat heading list) for a guide.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['guideId'], 'properties': {'guideId': {'type': 'string', 'description': 'ID of the guide'}}}
get_persona_brief
get_persona_brief
Read an AI persona and brand voice brief, poll until it is done
Returns the brief started by `POST /api/v1/tools/persona-brief`. While `status` is `pending`,
`fetching`, `analyzing` or `synthesizing`, call again every 3 seconds: `progress` and `pages`
show what has been read so far. When `status` is `done`, `brief` holds the structured brief,
`brief.writingPrompt` the ready-to-paste prompt and `markdown` the full document. When `status`
is `failed`, `failureReason` says why (NO_USABLE_PAGE, LLM_UNAVAILABLE, TIMEOUT, INTERNAL).
A page with a `failureReason` did not contribute to the brief. ANALYSIS_FAILED is the only one
on a page that was read: it keeps its `title` and `wordCount`, stays counted in
`progress.pagesFetched` and never enters `progress.pagesAnalyzed` nor `metrics`.
No quota is consumed. The `briefId` is random: whoever holds it can read the brief, which is
what makes share links work. Briefs expire after 90 days. Reads that are not attributed to an
account are subject to three anti-abuse counters, all per IP address and per UTC day:
the total number of requests, the reads of a single brief, and the number of different
briefs read. All three are far above any legitimate polling, including the busiest paid
account: crossing any of them returns 429 READ_RATE_LIMITED with `Retry-After`. Once the
cost ceiling is reached, further requests keep being refused until it resets, whether or
not they carry a valid briefId.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['briefId'], 'properties': {'briefId': {'type': 'string', 'description': 'The briefId returned by the creation call (22 characters).'}}}
get_tokens_usage
get_tokens_usage
Get API token usage costs for different endpoints
Returns the number of tokens required for each API endpoint operation.
Note: `eeatCompetitorsTokensCostPerCompetitor` is a **per-competitor** cost.
The total cost of POST /api/v1/eeat-competitors equals this value × the number of
competitors analyzed (deduplicated URLs in the guide's top-10 SERP, capped at 10).
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
get_usage
get_usage
Get current API usage and quota status
Returns the current period's API guide usage, quota limit, remaining count and the renewal date. Aligned on the Stripe subscription billing cycle. Does not consume credits.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
update_guide
update_guide
Update a guide
Updates editable fields of a specific guide (group, status, share state, linked URL, meta, hidden expressions). Only owners may update.
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'The ID of the guide to update'}, 'meta': {'type': 'object', 'properties': {'title': {'type': 'string'}, 'description': {'type': 'string'}}, 'description': 'SEO meta override for the guide', 'additionalProperties': {}}, 'group': {'type': 'string', 'description': 'Group/folder the guide belongs to (triggers cannibalisation analysis on previous and new group)'}, 'status': {'enum': ['', 'draft', 'active', 'review', 'published', 'archived'], 'type': 'string', 'description': 'Editorial status of the guide. Empty string clears the status.'}, 'linkedUrl': {'type': 'string', 'description': 'Public URL where the guide content is published (validated as URL)'}, 'shareState': {'enum': ['private', 'shared-read', 'shared-edit'], 'type': 'string', 'description': 'Sharing mode. Any value outside the enum is rejected with 400 (the check is case-sensitive). Plan must allow shared-read or shared-edit, otherwise 403 is returned.'}, 'hiddenExpressions': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Expressions to hide from the optimisation suggestions'}}}
History
Recent tool changes
Added
create_citation_check
Sept. 29, 2026, 2:51 a.m.
Added
get_citation_check
Sept. 29, 2026, 2:51 a.m.
Changed
create_score
Sept. 25, 2026, 2:51 a.m.
Changed
create_persona_brief
Sept. 23, 2026, 2:42 a.m.
Changed
create_score
Sept. 21, 2026, 2:50 a.m.
Changed
create_guides
Sept. 21, 2026, 2:50 a.m.
Changed
delete_guide
Sept. 21, 2026, 2:50 a.m.
Added
create_persona_brief
Sept. 21, 2026, 2:50 a.m.
Added
get_persona_brief
Sept. 21, 2026, 2:50 a.m.
Added
discover_persona_brief_pages
Sept. 21, 2026, 2:50 a.m.
Changed
get_eeat
Sept. 21, 2026, 2:50 a.m.
Added
create_score
Sept. 17, 2026, 12:40 p.m.
Added
delete_guides
Sept. 17, 2026, 12:40 p.m.
Added
create_guides
Sept. 17, 2026, 12:40 p.m.
Added
get_guides
Sept. 17, 2026, 12:40 p.m.
Added
delete_guide
Sept. 17, 2026, 12:40 p.m.
Added
update_guide
Sept. 17, 2026, 12:40 p.m.
Added
get_guide
Sept. 17, 2026, 12:40 p.m.
Added
get_credit_ledger
Sept. 17, 2026, 12:40 p.m.
Added
get_usage
Sept. 17, 2026, 12:40 p.m.
Added
get_tokens_usage
Sept. 17, 2026, 12:40 p.m.
Added
delete_outline
Sept. 17, 2026, 12:40 p.m.
Added
create_outline
Sept. 17, 2026, 12:40 p.m.
Added
get_outline
Sept. 17, 2026, 12:40 p.m.
Added
delete_meta
Sept. 17, 2026, 12:40 p.m.
Added
create_meta
Sept. 17, 2026, 12:40 p.m.
Added
get_meta
Sept. 17, 2026, 12:40 p.m.
Added
delete_internal_links
Sept. 17, 2026, 12:40 p.m.
Added
create_internal_links
Sept. 17, 2026, 12:40 p.m.
Added
get_internal_links
Sept. 17, 2026, 12:40 p.m.
Discover
Similar MCP servers
Hermoso
io.github.hermoso-ai/hermoso
Supports ad research, competitor analysis, video and static ad creation, campaign policy checks, content publishing, and performa…
Heista
co.heista/api
Analyzes video advertising, builds brand intelligence profiles, researches markets, and generates advertising scripts and creativ…
Spook SEO
com.tryspook/spook
Provides SEO analysis, keyword and content generation, AEO checks, ad copy tools and automated article generation and publishing.
VarynForge
com.varynforge/server
Supports SEO research and content planning through niche analysis, competitor and keyword research, opportunity discovery, and wr…
AfterLaunch: the agentic growth marketing engine
io.afterlaunch/agentic-growth-marketing
Runs growth-marketing workflows covering SEO, AI-search visibility, competitor analysis, content planning, distribution channels,…
RoboWrite
ai.robowrite/mcp
Supports brand setup, content briefs, AI-generated drafts, editorial review, quality checks, and publishing workflows.
ai-content-drop
com.aicontentdrop/ai-content-drop
Generates AI images, videos, UGC clips, avatars, and finished ads, while organizing creative assets and campaign boards.
Newswire Com
io.github.pipeworx-io/newswire-com
Searches and retrieves recent press releases from Newswire.com's public newsroom feed.