# Web search for your agent

Connect → Web search for your agent

# Web search and page reading for your coding agent

    A coding agent that can look things up writes less from memory. AxForge runs its own web search as
    an MCP server with two tools: `web_search` finds pages, `read_page` reads one as text. It
    comes with the Coder plans and Managed Endpoint plans and runs on your API key, at no extra cost.

    **Before you start**

        - An AxForge API key. Get one (a minute).

        - A Coder plan (Noob, Coder or Pro) or a Managed Endpoint plan on that key's account:
        the Coder plans.

        - A coding agent that speaks MCP over HTTP: Claude Code, OpenCode, or any other MCP client.

## Add it to your agent

### Claude Code

One command adds it for every project (`--scope user`):

```
claude mcp add --transport http --scope user axforge-search https://api.axforge.ai/v1/mcp --header "Authorization: Bearer orx_live_your_key_here"
```

`claude mcp list` then shows **axforge-search**. Ask Claude Code to look something up and it
        calls `web_search`.

### OpenCode

In `~/.config/opencode/opencode.json` (the file from the
        OpenCode guide), add an `mcp` block beside `provider`. It reads the key from the
        same environment variable:

```
"mcp": {
  "axforge-search": {
    "type": "remote",
    "url": "https://api.axforge.ai/v1/mcp",
    "headers": { "Authorization": "Bearer {env:AXFORGE_API_KEY}" }
  }
}
```

### Any other MCP client

Give it the address and one header:

```
Address   https://api.axforge.ai/v1/mcp
Header    Authorization: Bearer orx_live_your_key_here
```

It speaks MCP over plain HTTP (JSON-RPC), protocol versions 2024-11-05 to 2025-11-25.

## The two tools

        | Tool | What it does |  |

        | web_search | Finds pages for a query on AxForge's own search: their titles, addresses and a
        line of each. 8 results unless asked for more, 20 at most. |  |

        | read_page | Reads one page as text, up to 30,000 characters: `http` and
        `https` addresses on the web's own ports, 80 and 443, never an address on a private network. |  |

## Check that it works

    Ask your agent to search for something it cannot know from memory, such as this week's release
    of a library. The calls show in the console under API Keys → Recent
    calls within a minute, as `mcp/web_search` and `mcp/read_page`.

## When it does not work

      | What you see | What it means | Fix |  |

        | `401` | the key was refused | paste it again, whole, after `Bearer `, or make a new one |  |

        | "Web search comes with the Coder plans" | the key's account has no Coder plan or Managed Endpoint plan | take one in the console, Billing & Usage → Coder plans |  |

        | "not answering" | the search engines behind it did not answer | try again in a minute |  |

        | "This address cannot be read" | not an `http` or `https` page on port 80 or 443, or on a private network | nothing to fix: `read_page` reads public web pages only |  |

      ← llm
      How GPU rentals work →



Source: https://dev.axforge.ai/docs/connect/web-search/