Is this an official DHL Location Finder MCP server?

No. It is Memtro's MCP server with Memtro's DHL Location Finder connector behind it: the connector reads DHL Location Finder through its API with the credentials you connect on Dashboard → Connections, and DHL Location Finder publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in DHL Location Finder?

Not yet. Today every DHL Location Finder tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Shipping and delivery

DHL Location Finder MCP server

DHL Location Finder in any MCP client, through Memtro: DHL Location Finder does not publish this server. Memtro's DHL Location Finder connector reads DHL Location Finder through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Find DHL Service Points, lockers, post offices, PO boxes and post boxes near an address or a map coordinate, across both the parcel and express divisions, and look one up again by its location or keyword id. Each point comes back as DHL returns it, with the detail of its place and location left in DHL's own structure rather than renamed into fields nobody has checked. Read-only: this is the DHL Location Finder API, which has no writes, and it is the only DHL product this connector speaks to — not Express, not eCommerce, not Parcel DE, not tracking.

Reads

dhl_service_pointsDHL Service Points, lockers, post offices, PO boxes and post boxes near an address…
dhl_service_points_nearbyThe same search from a map coordinate rather than an address: DHL points within a radius of a latitude and longitude.
dhl_service_pointOne DHL point by its location id, as DHL returned it inside a result from the searches above.
dhl_service_point_by_keywordDHL points matching a keyword id — DHL's own identifier for a named shop or locker, of the kind quoted to a customer in a delivery notice.

Connect it

First connect DHL Location Finder on Dashboard → Connections, then add Memtro to your client once. The DHL Location Finder tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared DHL Location Finder connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Use the DHL Location Finder tools to DHL Service Points, lockers, post offices, PO boxes and post boxes near an address
› Use the DHL Location Finder tools to the same search from a map coordinate rather than an address: DHL points within a radius of a latitude and longitude
› Use the DHL Location Finder tools to one DHL point by its location id, as DHL returned it inside a result from the searches above
› Use the DHL Location Finder tools to DHL points matching a keyword id — DHL's own identifier for a named shop or locker, of the kind quoted to a customer in a delivery notice

Questions

Is this an official DHL Location Finder MCP server?: No. It is Memtro's MCP server with Memtro's DHL Location Finder connector behind it: the connector reads DHL Location Finder through its API with the credentials you connect on Dashboard → Connections, and DHL Location Finder publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in DHL Location Finder?: Not yet. Today every DHL Location Finder tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.