Forward Geocoder avatar
Forward Geocoder

Deprecated

Pricing

$1.00 / 1,000 results

Go to Store
Forward Geocoder

Forward Geocoder

Deprecated

Developed by

Poidata

Poidata

Maintained by Community

Quickly convert place names, addresses, or landmarks into coordinates. Forward Geocoder delivers fast, accurate latitude and longitude data for any location. Run via API, export results, schedule tasks, and integrate seamlessly into your workflows.

0.0 (0)

Pricing

$1.00 / 1,000 results

1

Total users

9

Monthly users

3

Runs succeeded

0%

Last modified

6 days ago

You can access the Forward Geocoder programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.apify.com/sse?actors=poidata/forward-geocoder",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Forward Geocoder

You have a few options for interacting with the MCP server:

  • Use mcp.apify.com via mcp-remote from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).

  • Set up the connection directly in your MCP client UI by providing the URL https://mcp.apify.com/sse?actors=poidata/forward-geocoder along with an API token (or use OAuth).

  • Connect to mcp.apify.com via Server-Sent Events (SSE), as shown below:

{
"mcpServers": {
"apify": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=poidata/forward-geocoder",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.