> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/nl/producttour-webapp/geopard-mcp/geopard-mcp-verbinding-verifieren.md).

# GeoPard MCP-verbinding verifiëren

Leer hoe u controleert of GeoPard MCP correct is verbonden voordat u workflows in een LLM uitvoert.

Voordat u met de GeoPard MCP-tool in Claude of ChatGPT werkt, is het belangrijk om te bevestigen dat de GeoPard MCP-connector actief is.

Een actieve verbinding stelt het systeem in staat om veldgegevens op te vragen, statistieken van datasets op te halen en nauwkeurige aanbevelingen te genereren. Als de connector niet is ingeschakeld, kunnen workflows mislukken of onvolledige resultaten opleveren.

Deze handleiding legt uit hoe u de verbindingsstatus controleert en GeoPard MCP activeert indien nodig.

## Anthropic Claude

{% @arcade/embed url="<https://app.arcade.software/share/r4pkyDVAVMsKOLo8iG47>" flowId="r4pkyDVAVMsKOLo8iG47" %}

## OpenAI ChatGPT

{% @arcade/embed url="<https://app.arcade.software/share/gWftgDqsOt8Rh5y8yS21>" flowId="gWftgDqsOt8Rh5y8yS21" %}


---

# 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.geopard.tech/geopard-tutorials/nl/producttour-webapp/geopard-mcp/geopard-mcp-verbinding-verifieren.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.