How to Use the Felt (Collaborative Maps) MCP in Cline

Q: Can Cline write code that interacts with my Felt (Collaborative Maps) layers?

Yes, Cline uses getlayer to inspect your layer schema and write matching integration code. It ensures your frontend code matches the live map structure.

Q: How does Cline handle map element deletion in Felt (Collaborative Maps)?

Cline invokes deleteelement when you tell it to clean up specific test markers. Cline uses the MCP server to target the elements by their IDs directly from your workspace.

Q: Can I check the status of my maps from the Cline chat?

Yes, Cline calls getmap to retrieve map details and display them directly in your chat sidebar. You see the current layers and elements instantly.

Let Cline build spatial features and update your Felt collaborative maps directly from your VS Code workspace.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Felt (Collaborative Maps) MCP to Cline

Create your Vinkius account to connect Felt (Collaborative Maps) to Cline and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Felt (Collaborative Maps) with Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

End-To-End Map Provisioning with Cline

The `create_map` tool gives Cline the ability to generate new shared maps as part of its coding tasks. You can ask Cline to build a mapping feature, and it will set up the actual Felt map first to test against. After creating the map, Cline pulls the map ID and writes it directly into your local configuration files. You don't have to copy-paste IDs between your browser and VS Code.

Automated Layer Integration

The `create_layer` tool allows Cline to upload shapefiles, CSVs, or KML files directly from your workspace directory. Cline checks your project files, detects geographic data, and sends it to the map. If the layer structure changes during development, Cline runs `update_layer` or `delete_layer` to clean up. This keeps your development maps in sync with your local code branch.

Workspace-Driven Element Updates

The `add_elements` tool enables Cline to populate your maps with markers based on code variables or test databases. Cline reads your local data arrays and generates the correct geographic elements on your layer. When debugging, Cline uses `get_map` to verify that elements exist and match your local state. This helps you catch coordinate mismatches or styling bugs before you commit your code.

Setup guide

Set up Felt (Collaborative Maps) MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type felt-collaborative-maps-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest Felt (Collaborative Maps) refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Felt. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Felt (Collaborative Maps) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Felt (Collaborative Maps) MCP in Cline

Open the Cline sidebar, click the MCP Servers icon, and add the server configuration. You can also paste the server block directly into your `cline_mcp_settings.json` file.

Yes, Cline uses `get_layer` to inspect your layer schema and write matching integration code. It ensures your frontend code matches the live map structure.

Cline invokes `delete_element` when you tell it to clean up specific test markers. Cline uses the MCP server to target the elements by their IDs directly from your workspace.

Yes, Cline calls `get_map` to retrieve map details and display them directly in your chat sidebar. You see the current layers and elements instantly.

Yes, all geographic files and shapefiles are processed in an ephemeral, isolated V8 sandbox. Your credentials are encrypted, and data is transmitted directly to Felt through the secure Vinkius MCP gateway.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript