> ## Documentation Index
> Fetch the complete documentation index at: https://docs.asobeast.com/llms.txt
> Use this file to discover all available pages before exploring further.

# The asobeast MCP server

> asobeast ships a read only Model Context Protocol server. It runs locally over stdio, authenticates with a personal API token and exposes 21 tools.

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.

```text theme={null}
Which of my tracked keywords lost more than five positions this week?
```

```text theme={null}
Summarize the open critical actions across my portfolio and tell me which app to work on first.
```

```text theme={null}
Compare my visibility against my top competitor in Germany over the last 30 days.
```

## 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

| Requirement                 | Notes                                                                      |
| --------------------------- | -------------------------------------------------------------------------- |
| A running asobeast instance | Reachable from the machine the agent runs on                               |
| A personal API token        | Mandatory. A boot preflight exits non zero without a valid one             |
| An MCP capable client       | Claude Code and Claude Desktop are documented here. Any stdio client works |

## Next

<Card title="Connect an agent" icon="cable" href="/mcp/setup">
  Both setup paths, client configuration and the two failures that catch everyone.
</Card>