01
Overview
Koala AI MCP lets a compatible AI assistant call Koala's SEO, research, analytics and content tools through one remote MCP endpoint. The beta launched September 16, 2026. This guide focuses on the setup job rather than repeating the full product overview.
Before connecting, check eligibility. Koala's dedicated MCP page says the beta is available to Professional plans and above for accounts that have joined the beta. Sign in to Koala, join from the Beta page when eligible, and keep the account session available for browser authorization.
The remote MCP endpoint documented by Koala is https://koala.sh/api/mcp. For clients that support remote HTTP MCP with OAuth, add that URL as the server and complete the browser sign-in. Koala says the standard flow does not require copying an API key.
For Claude Code, Koala documents the terminal command: claude mcp add --transport http koala-ai https://koala.sh/api/mcp. After adding it, run /mcp in a Claude Code session and approve the connection in the browser. Treat this command as launch-state documentation and recheck Koala's page if the client syntax changes.
02
Capabilities and workflow
For ChatGPT, Koala lists a browser Developer mode setup. For Codex and Cursor, the MCP page provides client-specific setup tabs. The durable part of the workflow is the same: add Koala's remote MCP endpoint, authenticate in the browser, and approve the capabilities the app should receive. Avoid copying UI labels from older screenshots because these clients change quickly.
Permissions matter. Koala added per-app permissions at launch, letting users choose the tools and brands each connected application can access and change those permissions later from the account page. Start with the narrowest access needed for the task. If an assistant only needs public keyword/SERP research, do not automatically expose every brand or first-party analytics property.
If you want the assistant to use your own Search Console or Google Analytics evidence, first link those properties in Brand DNA, then authorize them for the MCP connection. Koala says the assistant can retrieve Search Console clicks, impressions and average position by query/page as well as Analytics traffic, audience and indexing information. Its MCP page says those eleven first-party-data tools use no platform credits.
After authorization, verify read access before asking the agent to create or edit content. A sensible test sequence is: ask it to identify available Koala capabilities; perform one low-cost/public keyword or SERP lookup; if first-party data was authorized, request a narrow Search Console query; then confirm the returned property/site is the one you intended.
03
Access, pricing and requirements
Only after the connection is verified should you test write-capable workflows. Koala's September 16 changelog says MCP assistants can create KoalaWriter articles, check status, read them back, edit them and generate images. Use a disposable or clearly identified test draft first so an incorrect brand selection does not affect a real content queue.
If the MCP does not appear, check four things before assuming the server is down: the Koala account is on an eligible beta plan; the beta has been joined; the client supports remote HTTP MCP and OAuth; and browser authorization completed for the correct account. If a specific tool is unavailable, inspect the app's Koala permissions because launch-day per-app scoping can intentionally hide tools or brands.
The normal OAuth flow is preferable to pasting a long-lived API credential into configuration when the client supports it. Koala's conventional API still uses API keys for programmatic integration, but the MCP's advertised setup is browser sign-in with per-app authorization.
Finally, watch usage. Some MCP tools use no platform credits, while external data lookups and image/content operations can consume credits or word allowance. A successful connection does not mean every agent action is free.
04
Practical guidance and limitations
Quick checklist: eligible Professional+ beta account; join beta; add https://koala.sh/api/mcp; authorize in browser; scope tools and brands; link Search Console/Analytics only if needed; test read-only data; verify the correct site/brand; then test a draft creation workflow.
This setup information is based on Koala's live MCP page and September 16 changelog and should be rechecked while the feature remains in beta.
Sources
Primary and supporting sources
Use the linked documentation to check current pricing, access and product behaviour. The dates above describe this article; they do not guarantee that every vendor claim remains current.