Brave Search MCP Server vs Geoapify

A side-by-side look at the Brave Search MCP Server and Geoapify MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Brave Search MCP Server logoBrave Search MCP ServerSearch & Data Extraction · Remote HTTP/SSEWeb search capabilities using Brave's Search API56GoodAuth: api key requiredGeoapify logoGeoapifyLocation Services · Local subprocess (stdio)Geoapify MCP — wraps the Geoapify Location Platform (geoapify.com)59GoodAuth: not declared

Verdict: choose Brave Search MCP Server for search & data extraction work over a hosted endpoint; choose Geoapify for location services as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Brave Search MCP Server logoChoose Brave Search MCP Server when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: BRAVE_MCP_TRANSPORT.
  • You want tools like query, country, search_lang.
Explore Brave Search MCP Server

Geoapify logoChoose Geoapify when

  • You need dedicated capabilities in the Location Services domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like geocode, reverse_geocode, places.
Explore Geoapify

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBrave Search MCP Server logoBrave Search MCP ServerGeoapify logoGeoapify
CategorySearch & Data ExtractionLocation Services
Quality signal56/100 · Good59/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthAPI key requiredNot declared
PricingFreemiumNot declared
Required env varsBRAVE_MCP_TRANSPORTNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1,5220
Directory activity 12 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools544

Tools & capabilities

Brave Search MCP Server tools 54

  • query
  • country
  • search_lang
  • ui_lang
  • count
  • offset
  • safesearch
  • freshness
  • text_decorations
  • spellcheck
  • result_filter
  • goggles
  • +42 more on the listing page

Geoapify tools 4

  • geocodeForward geocoding: convert an address, place name, or freeform location text into geographic coordinates (latitude/longitude). Returns matched candidates with formatted address, lat, lon, country, city, and postcode. Example: geocode({ text: "1600 Amphitheatre Parkway, Mountain View, CA" })
  • reverse_geocodeReverse geocoding: convert latitude/longitude coordinates into the nearest street address. Returns formatted address, country, city, street, house number, and postcode. Example: reverse_geocode({ lat: 48.8584, lon: 2.2945 })
  • placesSearch for places and points of interest (POI) near a location, filtered by Geoapify category. Returns name, formatted address, categories, lat, lon, and distance from the center point. Example: places({ categories: "catering.restaurant", lat: 48.8584, lon: 2.2945, radius: 1000 })
  • routingRouting / directions: compute the distance and travel time between two points for a given travel mode (drive, walk, bicycle, transit). Returns distance in meters and time in seconds. Example: routing({ from_lat: 48.8584, from_lon: 2.2945, to_lat: 48.8606, to_lon: 2.3376, mode: "drive" })

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Brave Search MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "brave-brave-search-mcp-server": {
      "url": "http://127.0.0.1:8080/mcp"
    }
  }
}

Geoapify

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "geoapify": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-geoapify"
      ]
    }
  }
}

Frequently asked questions

Brave Search MCP Server is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. Geoapify belongs to Location Services and uses a local stdio subprocess. Pick Brave Search MCP Server for search & data extraction work and Geoapify for location services.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Brave Search MCP Server is listed as freemium — a free tier with paid plans. Auth: api key required. Geoapify has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add brave-brave-search-mcp-server and geoapify as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Brave Search MCP Server has a quality signal of 56/100 (Good) with 12 views, 0 installs and 1,522 GitHub stars. Geoapify has 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars.