# Install Help4GEO Skill and connect MCP

Use this guide when the user wants to set up Help4GEO for the current Agent.

## Setup request

Install or update the canonical Help4GEO Skill from:

`https://help4geo.com/integrate/skill.md`

After the Skill is installed and verified, immediately install or configure the Help4GEO MCP server connection in the same setup task. If a `help4geo` MCP connection already exists, verify it and update it only when needed. Do not finish after the Skill stage and do not require the user to start a separate MCP setup task.

Use the current Agent's native Skill installation mechanism. The default scope should make the Skill available to this Agent's normal future work. Do not assume a particular directory, JSON format, TOML format, CLI command, or configuration file.

Treat the installed Skill as a copied artifact, not as a live reference that updates automatically. When Help4GEO publishes a newer `version` in the canonical `skill.md`, replace the installed copy completely, then reload the Skill or restart the Agent session before using the new workflow. This update-and-reload step also applies when troubleshooting an Agent that still follows an older article or monitoring workflow.

Before writing:

1. Detect whether the Agent supports Skill installation and identify the default scope it uses.
2. Show the target scope and path, and show a diff or replacement summary when the host supports it.
3. Preserve the Skill name `help4geo` and use the exact canonical content from `skill.md`.
4. If the host cannot install Skills, provide manual Agent-specific instructions and report that no installation was performed.

After a successful write, verify that the Agent can discover or load the installed `help4geo` Skill and report the exact installed `version`. Then continue with the MCP stage below without ending the setup response.

## MCP connection stage

Use the current Agent's native MCP installation or configuration mechanism. Configure this connection:

```yaml
server: help4geo
transport: streamable-http
endpoint: https://mcp.help4geo.com/mcp
authentication:
  scheme: bearer
  header: Authorization
  value: "Bearer <YOUR_HELP4GEO_API_KEY>"
```

If an API key is required, guide the user to `https://help4geo.com/account/api-keys`, ask the user to provide or create the key, replace `<YOUR_HELP4GEO_API_KEY>` with the actual key, and write it directly into the MCP configuration file. Do not require an environment variable or use an environment-variable reference. Reload the MCP connection or restart the Agent session when needed. Verify the connection with `initialize` or a read-only `geo_brand_profile(get)` query.

The setup is complete only after both stages are handled. Report the installed Skill scope and source URL, then report the MCP configuration and verification result separately. If the Agent cannot perform either stage, provide manual Agent-specific steps for the missing stage and clearly state which stage was not completed.

## Expected result

The installed artifact is one runtime Skill named `help4geo`; the MCP server is configured as the connection used by that Skill. This installation guide is not intended to remain installed as a second Skill and should not be selected for ordinary Help4GEO business workflows.
