MCP server: Suiko in your AI assistant

Claude, ChatGPT, Claude Code, Cursor or any compatible assistant reads your verified facts and writing rules in Suiko, checks a text and requests a page update. One address and one key to paste, nothing to install.

CursorVS Code

What your assistant does with Suiko

01Write accurately
It reads your prices, lead times and rules before drafting.
02Review
It checks a text against the facts in your base, source included.
03Pick the pages
It reads which pages have the most to gain from an update.
04Launch and write
It requests the update of a page, or files a text for review. You approve in Suiko.

The fifteen tools

All of Suiko: the knowledge base, automatic updates and the editorial workflow. No tool approves an update or publishes: those two steps stay in Suiko.

get_accountPages left, contents this month, connected sites.
list_knowledge_factsYour verified facts, with source and dates.
get_writing_rulesYour style rules, SEO reminders, forbidden phrasings.
check_text_against_factsThe facts that concern a text, and the numbers not covered.
score_textSuiko’s score on a text, criterion by criterion.
list_pages_to_updateThe pages to refresh, ranked, with the reason.
request_updateRequests the update of a page.
list_proposalsThe proposals, by state.
get_proposalOne proposal in detail: verified facts, sources, score, content.
list_contentsThe editorial contents, with state, writer and score.
get_contentOne content: brief, facts on the subject, text, tags, history.
create_contentCreates a content with its complete brief.
submit_textFiles a text for review, facts checked, reviewer notified.
set_content_statusChanges the state of a content, never “published”.
get_performanceClicks, impressions and position of the pages produced with Suiko.

Connect your assistant

Address: https://app.getsuiko.com/api/mcp. Two ways in: with a Suiko account (claude.ai, ChatGPT), or with your organisation’s API key (Settings > API) for Claude Code and editors.

Claude Code

One command in the terminal. The tools are available from the next session.

claude mcp add --transport http suiko https://app.getsuiko.com/api/mcp \
  --header "Authorization: Bearer chk_…"

Cursor, VS Code, Windsurf

In the editor’s MCP file (.cursor/mcp.json, .vscode/mcp.json).

{
  "mcpServers": {
    "suiko": {
      "url": "https://app.getsuiko.com/api/mcp",
      "headers": { "Authorization": "Bearer chk_…" }
    }
  }
}

Claude and ChatGPT, with a Suiko account

In claude.ai (Settings > Connectors > Add custom connector) or in ChatGPT (Settings > Apps and connectors > Create), paste the server address. On first use, Suiko asks you to sign in and to authorise the assistant for your organisation. No key to handle; access is cut in Settings > API.

An example

A marketing lead, in Claude Code, with Suiko connected.

She“Write the pricing section of our Packs page.”
The assistantReads the rules and the “pricing” facts, drafts with the verified amounts.
She“Which blog page should be updated first? Launch it.”
The assistantReads the ranking, requests the update of the first page.
SuikoFixes the outdated facts at their source, files a proposal.
SheReviews, approves. The page is published.

The key

Created by an administrator in Settings > API, shown once, revoked in one click. It opens the facts, pages and proposals of the whole organisation.

Good to know

The server calls no AI: it reads your base and wakes the machine. The reasoning stays in your assistant.
Checking a text is a keyword match. A missing fact proves nothing.
An update request reserves one page of your balance; the page is only counted at publication.
Approving an update and publishing stay in Suiko, by a person.
Every call is logged in Settings > API (who, which tool, outcome). A problem is stated plainly to the assistant; a failure on Suiko’s side is reported to us at once. Every tool is replayed by a test bench before each release.