Skip to main content
asobeast ships a Model Context Protocol server. It is read only, it runs as a local stdio process on your own machine, it authenticates to your instance with a personal API token, and it exposes twenty one tools covering apps, keywords, positions, SERPs, audits, reviews, analytics, the request budget and the Action Center queue. That means you can point Claude Code or Claude Desktop at your self hosted asobeast and ask it questions in plain language instead of clicking through the dashboard.

​
What can you ask?

Specific questions work best, because the tools take app ids, countries and date windows.

​
Every tool is read only

Every tool wraps a GET on the HTTP API and is annotated readOnlyHint: true. There is no write path at all. Marking an action done is deliberately unavailable. An agent that can close its own recommendations can quietly clear a queue you never read, so the server proposes work and leaves the decision with you. That constraint is why the integration is safe to hand to an agent with broad permissions. The worst case is a wrong answer, not a changed instance.

​
What it is not

The MCP server holds no database, imports no scraper and contains no server framework code. It is a consumer of the HTTP API exactly like the web app, typed with the same @asobeast/shared contracts, which is what keeps its tool descriptions from drifting away from the API.

​
Requirements

​
Next

Connect an agent

Both setup paths, client configuration and the two failures that catch everyone.
Last modified on July 31, 2026