Felt (Collaborative Maps) MCP Server for VS Code CopilotGive VS Code Copilot instant access to 11 tools to Add Elements, Create Layer, Create Map, and more

Name: Felt (Collaborative Maps)
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Ask AI about this MCP Server for VS Code Copilot

Open in ChatGPT Open in Claude Open in Perplexity

The Felt (Collaborative Maps) MCP Server for VS Code Copilot is a standout in the Collaboration category — giving your AI agent 11 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

Classic Setup·json

{
  "mcpServers": {
    "felt-collaborative-maps": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Felt (Collaborative Maps) and 4,000+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Felt (Collaborative Maps) MCP Server

Connect Felt to your AI agent to take full control of your collaborative mapping workflows through natural conversation. This server allows you to manage maps, layers, and geographic elements without leaving your workspace.

GitHub Copilot Agent mode brings Felt (Collaborative Maps) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 11 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Map Management — List all accessible maps, create new ones with specific viewports, and retrieve detailed metadata or delete maps.
Data Uploads & Layers — Create layers by uploading geographic data (GeoJSON, CSV, KML) via public URLs and monitor their processing status.
Dynamic Styling — Update layer names and apply complex visual styles using the Felt Style Object (FSO) programmatically.
Element Manipulation — Add, update, or delete specific geographic features like points, lines, and polygons within your map layers.
Spatial Analysis Context — Fetch map and layer details to provide your AI with the necessary context for spatial reasoning.

The Felt (Collaborative Maps) MCP Server exposes 11 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 11 Felt (Collaborative Maps) tools available for VS Code Copilot

When VS Code Copilot connects to Felt (Collaborative Maps) through Vinkius, your AI agent gets direct access to every tool listed below — spanning gis, mapping, spatial-data, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

add

Add elements on Felt (Collaborative Maps)

Add elements to a Felt layer

create

Create layer on Felt (Collaborative Maps)

Supports GeoJSON, CSV, KML, Shapefiles, etc. Create a layer (Upload Data) to a Felt map

create

Create map on Felt (Collaborative Maps)

Create a new Felt map

delete

Delete element on Felt (Collaborative Maps)

Delete a Felt element

delete

Delete layer on Felt (Collaborative Maps)

Delete a Felt layer

delete

Delete map on Felt (Collaborative Maps)

Delete a Felt map

get

Get layer on Felt (Collaborative Maps)

Get details for a specific Felt layer

get

Get map on Felt (Collaborative Maps)

Get details for a specific Felt map

list

List maps on Felt (Collaborative Maps)

List Felt maps

update

Update element on Felt (Collaborative Maps)

Update a Felt element

update

Update layer on Felt (Collaborative Maps)

Update a Felt layer

Connect Felt (Collaborative Maps) to VS Code Copilot via MCP

Follow these steps to wire Felt (Collaborative Maps) into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Felt (Collaborative Maps)

Ask Copilot: "Using Felt (Collaborative Maps), help me...". 11 tools available

Why Use VS Code Copilot with the Felt (Collaborative Maps) MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Felt (Collaborative Maps) through the Model Context Protocol.

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

Felt (Collaborative Maps) + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Felt (Collaborative Maps) MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Felt (Collaborative Maps) in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Felt (Collaborative Maps) immediately.

"List all my current Felt maps."

"Create a new map titled 'Project Alpha' centered on San Francisco."

"Add a point element to layer `layer_abc` at [ -122.4, 37.8 ]."

Troubleshooting Felt (Collaborative Maps) MCP Server with VS Code Copilot

Common issues when connecting Felt (Collaborative Maps) to VS Code Copilot through Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Felt (Collaborative Maps) + VS Code Copilot FAQ

Common questions about integrating Felt (Collaborative Maps) MCP Server with VS Code Copilot.

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.