Bring Geospatial Ai
to VS Code Copilot
Learn how to connect Mapflow to VS Code Copilot and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Mapflow MCP Server?
Connect your Mapflow account to any AI agent and manage geospatial AI processing through natural conversation.
What you can do
- Project Management — Create and manage mapping projects
- Image Processing — Trigger AI models on satellite and drone imagery
- Task Tracking — Monitor processing status and completion
- Dataset Browsing — Access generated vector datasets and polygons
- Model Management — Browse available AI models (buildings, roads, forests)
How it works
1. Subscribe to this server
2. Enter your Mapflow API Key
3. Start processing geospatial data from Claude, Cursor, or any MCP-compatible client
Who is this for?
- GIS Specialists — extract vector data from imagery automatically
- Urban Planners — map buildings and infrastructure
- Environmentalists — monitor forests and land use
Built-in capabilities (7)
Pass data as a JSON string. Start a new imagery analysis
Pass data as a JSON string. Create a new project
Get processing result data
Check status of a processing job
List available geospatial AI models
List all geospatial processings
List all MapFlow projects
Why VS Code Copilot?
GitHub Copilot Agent mode brings Mapflow data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 7 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Mapflow in VS Code Copilot
Mapflow and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Mapflow to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Mapflow in VS Code Copilot
The Mapflow MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 7 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Mapflow for VS Code Copilot
Every tool call from VS Code Copilot to the Mapflow MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I process satellite imagery and extract vector data?
Yes. Trigger AI models on imagery to automatically extract buildings, roads, forests, and other features as vector polygons.
How does Mapflow authentication work?
Mapflow uses Bearer authentication against api.mapflow.ai/rest using your API Key.
Can I track processing tasks?
Yes. Monitor processing status, progress percentages, and access completion datasets when ready.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.