# Set up the Getnet MCP server

The Getnet docs come with a Model Context Protocol (MCP) server. Once your AI assistant is connected, it can search and read every page of this site, guides and API reference alike, always the published version instead of a stale training-data guess. No account or sign-up needed.

<Callout type="info">
  **Read-only, scoped to the docs**

  The MCP server searches and reads the **documentation**: product guides, integration steps and the API reference for every Getnet API. It can't call the Getnet APIs or see your merchant data. To make real requests, use your sandbox credentials from [API keys](/en/articles/api-keys).
</Callout>

## What you get

<CardGroup cols={2}>
  <Card title="Find the right page" icon="search">
    Ask in plain language and get pointed to the guide or endpoint that answers it, across Global API, Web Checkout, App2App, Integrated POS and more.
  </Card>

  <Card title="Read endpoints in full" icon="braces">
    Pull an endpoint's parameters, request and response schemas and examples straight from the API reference.
  </Card>

  <Card title="Answers in your language" icon="languages">
    Search English, Spanish or Portuguese pages, or filter to one of them.
  </Card>

  <Card title="Always up to date" icon="refresh-cw">
    Every answer is read from the docs as they're published right now.
  </Card>
</CardGroup>

## Quick setup

The Getnet MCP server lives at:

```
https://getnet.writedocs.io/mcp
```

Pick your tool below. No authentication is required.

<Tabs>
  <Tab title="Claude Code">

  Run:

  ```bash
  claude mcp add --transport http getnet https://getnet.writedocs.io/mcp
  ```

  </Tab>

  <Tab title="Claude Desktop">

  Go to **Settings → Connectors → Add custom connector**, then enter:

  - **Name:** `Getnet`
  - **URL:** `https://getnet.writedocs.io/mcp`

  </Tab>

  <Tab title="Cursor">

  Add to your project's or global `mcp.json`:

  ```json
  {
    "mcpServers": {
      "getnet": {
        "url": "https://getnet.writedocs.io/mcp"
      }
    }
  }
  ```

  </Tab>

  <Tab title="VS Code">

  Add to `.vscode/mcp.json`:

  ```json
  {
    "servers": {
      "getnet": {
        "type": "http",
        "url": "https://getnet.writedocs.io/mcp"
      }
    }
  }
  ```

  </Tab>

  <Tab title="Windsurf">

  Add to `~/.codeium/windsurf/mcp_config.json`:

  ```json
  {
    "mcpServers": {
      "getnet": {
        "serverUrl": "https://getnet.writedocs.io/mcp"
      }
    }
  }
  ```

  </Tab>
</Tabs>

Restart your editor or start a new chat, then confirm the connection by asking something only these docs would know, like *"Which endpoint creates a payment link in the Payment Link API?"*

<Callout type="tip">
  **One-click connect**

  Every page's contextual menu (top right of the page) also has **Copy MCP server URL**, **Connect to Cursor** and **Connect to VS Code**.
</Callout>

## Available tools

| Tool | What it does |
| :--- | :--- |
| `list_docs` | Lists every documentation page with its title, URL and description. |
| `search_docs` | Finds the pages that best match a question. Can be limited to one language (`en`, `es` or `pt`). |
| `get_doc` | Returns a page's full content as Markdown, including an API endpoint's parameters and schemas. Accepts one path or URL, or several. |

## Troubleshooting

<Accordion title="The server doesn't show up in my tool list">
  Confirm your config's JSON is valid (no trailing commas, every brace closed), then restart your editor or start a new session.
</Accordion>

<Accordion title="Answers seem out of date">
  Start a new conversation. MCP results reflect the latest published docs, but a long-running chat may still be reasoning from what it read earlier.
</Accordion>

<Accordion title="Answers come back in the wrong language">
  Say which language you want in your question, for example *"answer from the Spanish docs"*. Your assistant can pass that to `search_docs` as a language filter.
</Accordion>

## Get better answers

Ask specific, product-shaped questions instead of broad ones:

- Weaker: "How does Getnet work?"
- Stronger: "What fields does the Global API need for a 3-installment credit card payment?"

## Next steps

- New to Getnet? Start with [Choose your integration](/en/docs/general/getnet-solutions).
- Ready to build? Get your [API keys](/en/articles/api-keys) and follow the [Global API quickstart](/en/global-api/sep-api/first-steps-api/quickstart-api).