F
licenseB
qualityB
maintenanceProvides read-only query tools over OpenStreetMap data in PostGIS, enabling natural language queries for features, categories, and spatial analysis.
7
-
Wherobots
Server Details
Generate and run high performance queries on open and private spatial data at-scale in the cloud
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
- Changed
describe_table_tool5 fields changed- added
Output schema / properties / commentAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Table-level description/comment" +} - added
Output schema / properties / last_updatedAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Timestamp of the latest snapshot (ISO 8601)" +} - added
Output schema / properties / partition_columnsAdded value: +{ + "description": "Partition spec with resolved column names and transforms. Add partition filters on these columns to improve query performance.", + "items": { + "additionalProperties": { + "type": "string" + }, + "type": "object" + }, + "type": "array" +} - added
Output schema / properties / propertiesAdded value: +{ + "additionalProperties": { + "type": "string" + }, + "description": "User-set table properties (e.g. update frequency, source, query hints)", + "type": "object" +} - added
Output schema / properties / row_countAdded value: +{ + "anyOf": [ + { + "type": "integer" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Number of rows in the table" +}
- Removed
list_hierarchy_tool
3 tool updates
- Changed
describe_table_tool5 fields changed- removed
Output schema / $defsRemoved value: -{ - "NestedField": { - "properties": { - "doc": { - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "default": null - }, - "id": { - "type": "integer" - }, - "name": { - "type": "string" - }, - "required": { - "anyOf": [ - { - "type": "boolean" - }, - { - "type": "null" - } - ], - "default": false - }, - "type": { - "anyOf": [ - { - "type": "string" - }, - { - "additionalProperties": true, - "type": "object" - } - ] - } - }, - "required": [ - "id", - "name", - "type" - ], - "type": "object" - } -} - removed
Output schema / properties / schema / items / $refRemoved value: -"#/$defs/NestedField" - added
Output schema / properties / schema / items / propertiesAdded value: +{ + "doc": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null + }, + "id": { + "type": "integer" + }, + "name": { + "type": "string" + }, + "required": { + "anyOf": [ + { + "type": "boolean" + }, + { + "type": "null" + } + ], + "default": false + }, + "type": { + "anyOf": [ + { + "type": "string" + }, + { + "additionalProperties": true, + "type": "object" + } + ] + } +} - added
Output schema / properties / schema / items / requiredAdded value: +[ + "id", + "name", + "type" +] - added
Output schema / properties / schema / items / typeAdded value: +"object"
- Changed
list_hierarchy_tool9 fields changed- removed
Output schema / $defsRemoved value: -{ - "CatalogInfo": { - "properties": { - "databases": { - "additionalProperties": { - "$ref": "#/$defs/DatabaseInfo" - }, - "description": "Databases in the catalog.", - "type": "object" - } - }, - "required": [ - "databases" - ], - "type": "object" - }, - "DatabaseInfo": { - "properties": { - "tables": { - "description": "List of tables in the database.", - "items": { - "$ref": "#/$defs/TableInfo" - }, - "type": "array" - } - }, - "required": [ - "tables" - ], - "type": "object" - }, - "HierarchySummary": { - "properties": { - "catalogs_count": { - "description": "Total number of catalogs.", - "type": "integer" - }, - "databases_count": { - "description": "Total number of databases.", - "type": "integer" - }, - "tables_count": { - "description": "Total number of tables.", - "type": "integer" - } - }, - "required": [ - "catalogs_count", - "databases_count", - "tables_count" - ], - "type": "object" - }, - "TableInfo": { - "properties": { - "name": { - "description": "Name of the table.", - "type": "string" - } - }, - "required": [ - "name" - ], - "type": "object" - } -} - removed
Output schema / properties / hierarchy / additionalProperties / $refRemoved value: -"#/$defs/CatalogInfo" - added
Output schema / properties / hierarchy / additionalProperties / propertiesAdded value: +{ + "databases": { + "additionalProperties": { + "properties": { + "tables": { + "description": "List of tables in the database.", + "items": { + "properties": { + "name": { + "description": "Name of the table.", + "type": "string" + } + }, + "required": [ + "name" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "tables" + ], + "type": "object" + }, + "description": "Databases in the catalog.", + "type": "object" + } +} - added
Output schema / properties / hierarchy / additionalProperties / requiredAdded value: +[ + "databases" +] - added
Output schema / properties / hierarchy / additionalProperties / typeAdded value: +"object" - removed
Output schema / properties / summary / $refRemoved value: -"#/$defs/HierarchySummary" - added
Output schema / properties / summary / propertiesAdded value: +{ + "catalogs_count": { + "description": "Total number of catalogs.", + "type": "integer" + }, + "databases_count": { + "description": "Total number of databases.", + "type": "integer" + }, + "tables_count": { + "description": "Total number of tables.", + "type": "integer" + } +} - added
Output schema / properties / summary / requiredAdded value: +[ + "catalogs_count", + "databases_count", + "tables_count" +] - added
Output schema / properties / summary / typeAdded value: +"object"
- Changed
search_documentation_tool5 fields changed- removed
Output schema / $defsRemoved value: -{ - "DocumentResult": { - "properties": { - "content": { - "description": "Document content", - "type": "string" - }, - "metadata": { - "additionalProperties": true, - "description": "Arbitrary metadata", - "type": "object" - }, - "path": { - "description": "Document path or URL", - "type": "string" - } - }, - "required": [ - "content", - "path" - ], - "type": "object" - } -} - removed
Output schema / properties / results / items / $refRemoved value: -"#/$defs/DocumentResult" - added
Output schema / properties / results / items / propertiesAdded value: +{ + "content": { + "description": "Document content", + "type": "string" + }, + "metadata": { + "additionalProperties": true, + "description": "Arbitrary metadata", + "type": "object" + }, + "path": { + "description": "Document path or URL", + "type": "string" + } +} - added
Output schema / properties / results / items / requiredAdded value: +[ + "content", + "path" +] - added
Output schema / properties / results / items / typeAdded value: +"object"
8 tool updates
- First observed
describe_table_tool - First observed
execute_query_tool - First observed
generate_spatial_query_tool - First observed
list_catalogs_tool - First observed
list_databases_tool - First observed
list_hierarchy_tool - First observed
list_tables_tool - First observed
search_documentation_tool
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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!
Related MCP Connectors
Ask in plain English, get a rendered, shareable map from live public data. 24 geospatial tools.
A collaborative substrate over your data: vector, knowledge graph, SQL, geospatial, streaming.
Geospatial AI MCP server — satellite imagery, embeddings, weather, GNS governance
Query BigQuery, Snowflake, Redshift & Azure Synapse with natural language
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables spatial analysis of large remote GeoParquet files directly from object storage without downloading or importing data, using DuckDB's predicate and projection pushdown to answer queries efficiently.8MIT
- AlicenseNot gradedqualityDmaintenanceProduction-ready satellite imagery analysis server that enables natural language queries for Earth observation data, including land cover classification, vegetation monitoring, water detection, change detection, and automated environmental reporting.MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that connects AI agents to cloud-native geospatial data via STAC metadata and DuckDB with H3 spatial indexing, enabling zero-configuration SQL queries on terabyte-scale datasets over S3.23BSD 3-Clause
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.5/5.0
Disambiguation5/5
Each tool has a clear, distinct purpose: describing tables, executing queries, generating spatial queries, listing catalogs/databases/tables, and searching documentation. No overlap or ambiguity.
Naming Consistency5/5
All tools follow a consistent snake_case naming pattern ending with '_tool', e.g., describe_table_tool, execute_query_tool. Very predictable.
Tool Count5/5
7 tools cover essential operations for a spatial SQL database server: data discovery, schema inspection, query execution, query generation, and documentation search. Well-scoped for its purpose.
Completeness4/5
Covers the full read/exploration workflow. Missing DDL/DML tools (create/insert/update/delete) but those are likely out of scope for this server. Minor gap: no tool to list views or functions.