Wheremind
ai.wheremindv1.0.0Updated Oct 5, 2026
Hosted MCP for live place search, geocoding & turn-by-turn routes. No Maps API key to manage.
Overview
AI-generated overview
Hosted MCP server that gives an assistant live place search, geocoding, and turn-by-turn routing without a maps API key.
- What it does
- Wheremind is a remote MCP endpoint that provides location capabilities to an assistant: searching for places, converting addresses to and from coordinates (geocoding), and retrieving turn-by-turn routes. It is hosted by the provider, so the assistant connects to a remote URL rather than running a local package. The manifest lists no tools, so the exact tool names and parameters are not documented here.
- When to use it
- Worth adding when an assistant needs to answer location questions, look up places or addresses, or produce directions as part of a task. It suits users who want mapping features without signing up for or managing a separate maps API key.
- Requirements
- A remote MCP client that supports streamable HTTP, connecting to the provider's hosted endpoint. No packages, environment variables, headers, or authentication are declared in the manifest, and no maps API key is said to be needed.
Before you install
The service is remote, so place queries, addresses, and route requests are sent to the provider rather than processed locally. The manifest declares no authentication, so it is unclear how access is controlled or whether usage is metered or billed; confirm the provider's terms before relying on it.
Installation
In SourceWeft
- Open Wheremind in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"wheremind": {
"type": "http",
"url": "https://wheremind.ai/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 5, 2026