> For the complete documentation index, see [llms.txt](https://docs.exoclick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exoclick.com/mcp/ja/exoclick-mcp.md).

# ExoClick MCPサーバー

ExoClick MCP Serverを使用すると、Claude、ChatGPT、Cursor、または任意のカスタムエージェントなどのAIアシスタントを、Model Context Protocol（MCP）を通じてExoClickアカウントに直接接続できます。接続すると、キャンペーン、ゾーン、サイトのパフォーマンスについて自然な言葉で質問でき、コードを書いたり独自の連携を構築したりしなくても即座に回答を得られます。

{% hint style="info" %}
ExoClick MCP Serverは現在、積極的に開発が進められています。&#x20;

現時点では、 **広告主およびパブリッシャーの統計、広告主の設定、パブリッシャーのサイト／ゾーン設定への読み取りアクセス。**&#x20;

また、 **広告主はキャンペーンを作成・更新でき、パブリッシャーはサイトとゾーンを作成・更新できます。**

**各アカウントは自分のデータのみを照会でき、各ユーザーは接続時にAIクライアントに何を許可するかを選択します。**&#x20;
{% endhint %}

次のページでは、MCPが何を行うのか、そして接続方法を説明します。

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.exoclick.com/mcp/ja/exoclick-mcp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
