maptiler
Server Details
Geocoding, elevation, IP geolocation and coordinate transforms from the MapTiler Cloud API.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
8 toolsmaptiler_batch_geocodeBatch forward geocodeRead-onlyInspect
Forward-geocode up to 50 queries in one request. Returns a JSON ARRAY of GeoJSON FeatureCollections, one per query, in order. API: GET /geocoding/{q1;q2;...}.json.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results per query (1-10). | |
| types | No | Comma-separated place types to include. | |
| country | No | Comma-separated ISO 3166-1 alpha-2 country codes to restrict to. | |
| queries | Yes | 1-50 place/address strings to geocode. | |
| language | No | Comma-separated ISO 639-1 language codes for results. | |
| worldview | No | Disputed-border worldview: default | auto | ch | us. | |
| autocomplete | No | Treat the last term of each query as a prefix. |
maptiler_geocodeForward geocode (search place by name)Read-onlyInspect
Search for a place, address, or POI by name and get matching locations as GeoJSON features. e.g. 'Zurich' or '1600 Pennsylvania Ave'. API: GET /geocoding/{query}.json.
| Name | Required | Description | Default |
|---|---|---|---|
| bbox | No | Bounding box "west,south,east,north" to restrict results. | |
| limit | No | Max results (1-10). Default 5. | |
| query | Yes | Place/address/POI to search for (goes in the URL path). | |
| types | No | Comma-separated place types to include (e.g. address,poi,city). | |
| country | No | Comma-separated ISO 3166-1 alpha-2 country codes to restrict to. | |
| language | No | Comma-separated ISO 639-1 language codes for results. | |
| proximity | No | Bias toward a point: "lon,lat" or the literal "ip". | |
| worldview | No | Disputed-border worldview: default | auto | ch | us. | |
| fuzzyMatch | No | Allow approximate matching of the query terms. | |
| autocomplete | No | Treat the last term as a prefix for as-you-type search. | |
| excludeTypes | No | If true, `types` becomes an exclude list instead. |
maptiler_geolocate_ipGeolocate IP addressRead-onlyInspect
Geolocates the IP address making the request — from a hosted Worker this is the server's egress IP, not the end-user's. API: GET /geolocation/ip.json.
| Name | Required | Description | Default |
|---|---|---|---|
| elevation | No | Include elevation of the located point. |
maptiler_get_data_featuresGet dataset features (GeoJSON)Read-onlyInspect
Fetch the GeoJSON FeatureCollection of a MapTiler-hosted dataset by its data id. API: GET /data/{dataId}/features.json.
| Name | Required | Description | Default |
|---|---|---|---|
| dataId | Yes | MapTiler dataset id (from your MapTiler Cloud account). |
maptiler_get_elevationGet elevation at coordinatesRead-onlyInspect
Look up ground elevation at up to 50 coordinates. Returns an array of [lng, lat, elevation] triples. API: GET /elevation/{locations}.json.
| Name | Required | Description | Default |
|---|---|---|---|
| unit | No | Elevation unit. Default meters. | |
| locations | Yes | 1-50 [longitude, latitude] pairs (latitude -85..85). |
maptiler_reverse_geocodeReverse geocode (place at coordinates)Read-onlyInspect
Find the place(s) at a given longitude/latitude, returned as GeoJSON features. API: GET /geocoding/{longitude},{latitude}.json.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (1-10). Default 5. | |
| types | No | Comma-separated place types to include. | |
| language | No | Comma-separated ISO 639-1 language codes for results. | |
| latitude | Yes | Latitude, -90..90. | |
| longitude | Yes | Longitude, -180..180. | |
| worldview | No | Disputed-border worldview: default | auto | ch | us. | |
| excludeTypes | No | If true, `types` becomes an exclude list instead. |
maptiler_search_coordinate_systemsSearch coordinate reference systemsRead-onlyInspect
Search MapTiler's CRS/EPSG database by free text or key:value filters (e.g. 'code:4326', 'kind:CRS-PROJCRS'). API: GET /coordinates/search/{query}.json.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (1-50). Default 10. | |
| query | Yes | Search terms; supports filters like "code:4326" or "kind:CRS-PROJCRS". | |
| offset | No | Pagination offset. Default 0. | |
| exports | No | Include WKT / Proj4 export strings for each CRS. | |
| transformations | No | Include available transformations for each CRS. |
maptiler_transform_coordinatesTransform coordinates between CRSRead-onlyInspect
Transform up to 50 coordinate pairs from a source coordinate reference system to a target one (EPSG codes). API: GET /coordinates/transform/{coordinates}.json.
| Name | Required | Description | Default |
|---|---|---|---|
| ops | No | Pipe-separated transformation operation codes to force a path. | |
| s_srs | No | Source CRS / EPSG code. Default 4326 (WGS84). | |
| t_srs | No | Target CRS / EPSG code. Default 4326 (WGS84). | |
| coordinates | Yes | 1-50 [x, y] coordinate pairs in the source CRS. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!