+
Kimi K3 + Wayfern
Kimi Code runs K3 with a context of one million tokens, so long pages and big tables fit. Getting those pages from sites that block bots is the hard part.
Wayfern scrapes them, crawls whole sections and extracts tables in an anti-detect browser. Kimi reads the result, cleans it and writes the file.
› /mcp-config login wayfern
✓ wayfern connected · OAuth
› Extract the first 60 listings on
shop.acme.dev/pour-over into a CSV
Used extract_data (wayfern)
urls: …/pour-over?page=1, 2, 3
prompt: "title, price, rating, reviews"
60 items · credits_charged: 3
Used WriteFile (pour-over.csv)
pour-over.csv · 60 rows
Setup
Kimi Code runs on your computer and calls Wayfern over the remote server.
Then start kimi and run /login. Homebrew and npm also work.
bash
curl -fsSL https://code.kimi.com/kimi-code/install.sh | bashOr run /mcp-config in kimi. An entry with url and no transport is Streamable HTTP.
~/.kimi-code/mcp.json
{
"mcpServers": {
"wayfern": { "url": "https://api.wayfern.com/mcp" }
}
}Run this in kimi, then sign in on wayfern.com and click Allow. /mcp shows the status.
prompt
/mcp-config login wayfernprompt
Call get_usage on Wayfern and tell me my credit balance.Set WAYFERN_API_TOKEN to a token with the mcp scope. Kimi Code sends it as a Bearer token.
~/.kimi-code/mcp.json
{
"mcpServers": {
"wayfern": {
"url": "https://api.wayfern.com/mcp",
"bearerTokenEnvVar": "WAYFERN_API_TOKEN"
}
}
}Kimi Code loads skills from ~/.kimi-code/skills and ~/.agents/skills. The skill needs WAYFERN_API_TOKEN in the environment.
bash
mkdir -p ~/.kimi-code/skills/wayfern
curl -fsSL https://wayfern.com/skills/wayfern/SKILL.md -o ~/.kimi-code/skills/wayfern/SKILL.mdkimi.com has no custom MCP servers. Kimi Work's Plugin Builder makes a plugin from an MCP URL; its sign-in to Wayfern is not tested.
Route
Kimi Code signs in to remote MCP servers with OAuth, and K3's context holds long tool results. A large crawl stays in Wayfern until Kimi reads it with crawl_status.
/mcp-config login wayfern.bearerTokenEnvVar reads a wf_ token from a variable.~/.kimi-code/skills/wayfern. The Bash tool runs curl.api.wayfern.com/api/v1 directly.Example tasks
01
“Extract title, price, rating and review count of the first 60 listings on this public shop search page. Save them as pour-over.csv.”
extract_data bills 1 credit for each uncached source page.
02
“Crawl the product section of example-supplier.com, 200 pages at most, and write one JSON row per product.”
crawl_site bills 1 credit a page. crawl_status reads the results for free.
03
“Read the English and the German page of our 12 products and list each price or spec that differs.”
scrape_page at 1 credit a page: 24 credits for this job.
04
“Map example.com and count its URLs by top-level folder.”
map_site bills 2 credits for each 10 URLs.
Tools
The same tools on every route, at the REST API rates. Every result reports credits_charged.
kimi -p runs with auto permissions. Project MCP servers stay off until you trust the folder with KIMI_CODE_TRUST_WORKSPACE=1.kimi mcp add exists only in the archived Python kimi-cli. Kimi Code uses mcp.json or /mcp-config.Sign in once and the tools appear. Tool calls use the credits of your Wayfern plan, at the same rates as the API.