Data & Analytics · Felt + Claude
Felt MCP with Claude: Create and Share Interactive Maps Through Natural Language
The short answer
Claude works with Felt through the Model Context Protocol (MCP), an open standard that lets Claude securely use Felt on your behalf. Once connected with an API key, Claude can create maps, add layers, update geospatial data and share interactive maps, all through plain-language instructions your team controls.
What is Felt?
Felt is a modern GIS platform for creating, editing and sharing interactive maps. It is designed for teams that work with geospatial data and need a simple way to build maps together. Typical users include operations planners, GIS analysts, field teams, real estate and logistics staff, and public sector groups. Felt helps them turn location data into maps that colleagues and clients can explore in a browser without specialist software.
How Claude connects to Felt through MCP
The Model Context Protocol (MCP) is an open standard that acts as a universal adapter between Claude and other software. It lets Claude use a tool such as Felt in a structured, secure way, with the permissions the organisation sets. Instead of copying data by hand between systems, your team can describe what it needs in plain language and Claude carries out the steps within Felt.
Once connected, Claude can typically read existing maps and layers, create new maps, add layers from supplied data, update geospatial information and prepare maps for sharing. For example, a planner could ask Claude to build a map of service visits for the week and add a layer showing completed jobs. The scope of what Claude can do depends on the access granted to the API key.
Permissions and approvals keep people in charge. Access is limited to what the workflow needs, and actions that change or publish shared maps can require a named person to approve them first. Every action can be logged, so your team can see what was changed, when and by which process.
What you can automate
Weekly field service maps
Operations managers often need an up-to-date view of where crews are working. Claude can gather job locations from a supplied data source, add them as a layer in Felt and update the map each week. Dispatchers then open one interactive map instead of reconciling several spreadsheets, saving time and reducing errors in routing discussions.
Property and site portfolio views
Real estate and facilities teams can use Claude to create maps of properties, leases or sites, with layers for status, size or renewal dates. Account managers can share the link with clients, who explore the portfolio on their own. Updates to site data flow into the map without rebuilding it from scratch.
Client-ready location reports
Consultants and sales teams frequently need to show clients where things are. Claude can assemble a Felt map from a brief, add the relevant layers and prepare a clean shareable version. This shortens the time between a meeting request and a professional visual, while the consultant reviews the output before it goes out.
Public consultation and community maps
Public sector and community organisations can use Felt to show planned works, facilities or survey results. Claude can build and update these maps from staff instructions, keeping the public view current. Staff approve each published version so that only checked information reaches residents.
Logistics and delivery zone planning
Logistics planners can ask Claude to map delivery zones, depots and customer clusters, and to add layers that show capacity or coverage gaps. Planners then test scenarios by asking for new layers, which helps them compare options quickly before committing to changes.
An end-to-end workflow: Weekly service coverage map from CRM and ticketing data
TriggerEvery Monday at 07:00, or when the operations lead requests a refresh
Claude pulls the latest customer site records and open service tickets from the CRM and ticketing system, as permitted by the workflow.
Claude checks addresses and flags records with missing or unclear locations for a person to review.
Claude creates or updates a Felt map and adds layers for open tickets, completed visits and overdue jobs.
Claude prepares a summary of coverage gaps and posts it to the operations team channel in Microsoft 365.
The operations lead reviews the map and approves sharing it with regional managers.
Claude shares the approved interactive map through Felt and records the action in the audit log.
OutcomeRegional managers get a current, shared map of service coverage each week without manual data assembly. Operations leads spend their time acting on gaps rather than preparing reports, and every published map has a named approver.
How we set it up
Free automation audit
We review how your team currently builds and shares maps, and identify the workflows where Claude and Felt would save the most time. You receive a short written summary of priorities at no cost.
Secure API key connection
We connect Claude to Felt using an API key, stored securely and scoped to the minimum access the workflow needs. Your IT team keeps control of the key and can revoke it at any time.
Workflow design and approvals
We design the end-to-end workflow across Felt and your other systems, such as Microsoft 365, CRM or ticketing. We define which actions run automatically and which need a person's approval before anything is changed or shared.
Testing with real cases
We test the setup against past examples from your own data, checking map accuracy, layer updates and sharing behaviour. We fix issues before anything goes live.
Launch, monitoring and training
We launch with audit logs and monitoring in place, then train your team on how to request maps, review outputs and approve shared versions. Support continues during the first weeks of use.
Who benefits
- Operations and logistics managers
- Current maps of crews, deliveries or sites without rebuilding them each week.
- GIS analysts and data teams
- Less repetitive map building, so more time for analysis and data quality.
- Sales and account managers
- Professional location visuals for clients, prepared quickly and reviewed before sending.
- IT and compliance leaders
- Scoped API access, approval steps and audit logs that keep data use visible and controlled.
Security and control
- API access is limited to the permissions the workflow needs, and keys are stored securely and can be revoked.
- Actions that change or publish shared maps require approval from a named person.
- Every action Claude takes in Felt is logged for review, so changes can be traced.
- Location data is checked for missing or unclear records before it is mapped.
- Sharing settings are reviewed before any map is made available outside the organisation.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can use Claude with Felt under their existing data protection and privacy arrangements. In India, the Digital Personal Data Protection Act, 2023 governs personal data, and we design workflows to match it. Organisations in the UAE and Saudi Arabia must meet local data protection laws, and we select a hosting region for custom applications to meet those requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Felt MCP server do?
The Felt MCP server gives Claude a secure way to work with Felt. Through it, Claude can typically create maps, add layers, update geospatial data and share interactive maps when instructed in plain language. It acts as a controlled connection, so Claude only uses the functions that the access settings allow.
Is connecting Claude to Felt secure?
The connection is designed around least-privilege access. We use an API key stored securely, limit it to the functions the workflow needs and add approval steps for changes and sharing. Logs record activity, and your IT team can revoke access at any time. Security also depends on your own policies, which we review during the audit.
What can Claude do with Felt once connected?
Typically Claude can read existing maps, create new ones, add layers from supplied data, update geospatial information and prepare maps for sharing. The exact range depends on the access granted and the workflow designed. Anything that changes or publishes a shared map can be set to require a person's approval first.
How long does setup take?
Timelines vary with the number of workflows and the systems involved. A focused setup covering one or two workflows often takes a few weeks, including testing and training. The free automation audit gives a clearer estimate for your organisation.
Which plan or permissions do I need in Felt?
Generally, you need an account in Felt that allows API key creation, and the key must have permissions for the actions you want Claude to perform. Requirements depend on your Felt setup, so we confirm them during the audit and advise your administrator on the appropriate settings.