Felt (Collaborative Maps) MCP Server for Google ADKGive Google ADK 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

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Felt (Collaborative Maps) as an MCP tool provider through Vinkius and your ADK agents can call every tool with full schema introspection.

Ask AI about this MCP Server for Google ADK

Open in ChatGPT Open in Claude Open in Perplexity

The Felt (Collaborative Maps) MCP Server for Google ADK 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

python

from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
    StreamableHTTPConnectionParams,
)

# Your Vinkius token. get it at cloud.vinkius.com
mcp_tools = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    )
)

agent = Agent(
    model="gemini-2.5-pro",
    name="felt_collaborative_maps_agent",
    instruction=(
        "You help users interact with Felt (Collaborative Maps) "
        "using 11 available tools."
    ),
    tools=[mcp_tools],
)

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.

Google ADK natively supports Felt (Collaborative Maps) as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 11 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

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 Google ADK 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 Google ADK

When Google ADK 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 Google ADK via MCP

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

Install Google ADK

Run pip install google-adk

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Create the agent

Save the code above and integrate into your ADK workflow

Explore tools

The agent will discover 11 tools from Felt (Collaborative Maps) via MCP

Why Use Google ADK with the Felt (Collaborative Maps) MCP Server

Google ADK provides unique advantages when paired with Felt (Collaborative Maps) through the Model Context Protocol.

Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Felt (Collaborative Maps)

Production-ready features like session management, evaluation, and deployment come built-in. not bolted on

Seamless integration with Google Cloud services means you can combine Felt (Collaborative Maps) tools with BigQuery, Vertex AI, and Cloud Functions

Felt (Collaborative Maps) + Google ADK Use Cases

Practical scenarios where Google ADK combined with the Felt (Collaborative Maps) MCP Server delivers measurable value.

Enterprise data agents: ADK agents query Felt (Collaborative Maps) and cross-reference results with internal databases for comprehensive analysis

Multi-modal workflows: combine Felt (Collaborative Maps) tool responses with Gemini's vision and language capabilities in a single agent

Automated compliance checks: schedule ADK agents to query Felt (Collaborative Maps) regularly and flag policy violations or configuration drift

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Felt (Collaborative Maps)

Example Prompts for Felt (Collaborative Maps) in Google ADK

Ready-to-use prompts you can give your Google ADK 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 Google ADK

Common issues when connecting Felt (Collaborative Maps) to Google ADK through Vinkius, and how to resolve them.

McpToolset not found

Update: pip install --upgrade google-adk

Felt (Collaborative Maps) + Google ADK FAQ

Common questions about integrating Felt (Collaborative Maps) MCP Server with Google ADK.

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.