> 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/pt-br/tour-do-produto-aplicativo-web/geopard-mcp/verificar-conexao-do-geopard-mcp.md).

# Verificar Conexão do GeoPard MCP

Aprenda como verificar se o GeoPard MCP está conectado corretamente antes de executar fluxos de trabalho em um LLM.

Antes de trabalhar com a ferramenta GeoPard MCP no Claude ou no ChatGPT, é importante confirmar que o conector GeoPard MCP está ativo.

Uma conexão ativa permite que o sistema solicite dados do campo, recupere estatísticas do conjunto de dados e gere recomendações precisas. Se o conector não estiver habilitado, os fluxos de trabalho podem falhar ou retornar resultados incompletos.

Este guia explica como verificar o status da conexão e ativar o GeoPard MCP, se necessário.

## 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/pt-br/tour-do-produto-aplicativo-web/geopard-mcp/verificar-conexao-do-geopard-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.