Brave Search MCP Server vs Tomtom

A side-by-side look at the Brave Search MCP Server and Tomtom 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 requiredTomtom logoTomtomLocation Services · Local subprocess (stdio)TomTom MCP — wraps the TomTom Search & Routing APIs (api.tomtom.com)59GoodAuth: not declared

Verdict: choose Brave Search MCP Server for search & data extraction work over a hosted endpoint; choose Tomtom 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

Tomtom logoChoose Tomtom when

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBrave Search MCP Server logoBrave Search MCP ServerTomtom logoTomtom
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,5230
Directory activity 13 views 0 installs 0 upvotes 2 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

Tomtom tools 4

  • geocodeGeocoding: convert an address, place name, or free-text location query into geographic coordinates (latitude/longitude). Returns formatted address, country, lat, lon, type, and match score. Example: geocode({ query: "350 5th Ave, New York" })
  • search_poiSearch for points of interest (POIs) — businesses, landmarks, restaurants, gas stations, etc. — by name or category, optionally near a lat/lon center within a radius. Returns name, category, address, coordinates, phone, url, and distance. Example: search_poi({ query: "coffee", lat: 40.748, lon: -73.985, radius: 1000 })
  • reverse_geocodeReverse geocoding: convert latitude/longitude coordinates into a human-readable street address. Returns the freeform address, country, municipality, street name, postal code, and position. Example: reverse_geocode({ lat: 40.748, lon: -73.985 })
  • routeTraffic-aware routing / directions: calculate the best route between two points and return distance plus travel time computed with live traffic. Reports traffic delay so you get realistic ETAs, not free-flow estimates. Supports car, truck, pedestrian, and bicycle travel modes. Example: route({ from_lat: 40.748, from_lon: -73.985, to_lat: 40.689, to_lon: -74.044 })

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"
    }
  }
}

Tomtom

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

Frequently asked questions

Brave Search MCP Server is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. Tomtom belongs to Location Services and uses a local stdio subprocess. Pick Brave Search MCP Server for search & data extraction work and Tomtom 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. Tomtom 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 tomtom 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 13 views, 0 installs and 1,523 GitHub stars. Tomtom has 59/100 (Good) with 2 views, 0 installs and 0 GitHub stars.