Tilebox
Query geospatial datasets, inspect workflow jobs, deploy published releases, and search Tilebox documentation.
- Brand
- Unknown
- Category
- Pending
- Primary Subcategory
- Pending
Integration details
Description
Connect your AI assistant to your Tilebox team. Discover datasets, inspect their schemas, and query datapoints by time and area. Inspect workflow jobs, tasks, logs, and traces. Manage datasets, workflows, and clusters, and deploy releases that have already been published. Search Tilebox documentation for setup instructions and API examples. Requires a Tilebox account and access to a team. Connect using OAuth and select the team to authorize. The server includes tools that create, change, and delete resources, so review requested actions before approving them. Building local workflow code, uploading artifacts, and publishing new releases require the Tilebox CLI rather than this MCP server. Deploying a published release does not start compute; compatible runners are needed for tasks to execute.
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- Account required
- First tracked
- 2026-09-30
- Tool count
- 36
- Geography
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competitive lineup
36 tools agents can invoke
How do I improve a Community connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.