# How to integrate Felt MCP with Claude Code

```json
{
  "title": "How to integrate Felt MCP with Claude Code",
  "toolkit": "Felt",
  "toolkit_slug": "felt",
  "framework": "Claude Code",
  "framework_slug": "claude-code",
  "url": "https://composio.dev/toolkits/felt/framework/claude-code",
  "markdown_url": "https://composio.dev/toolkits/felt/framework/claude-code.md",
  "updated_at": "2026-05-12T10:11:13.566Z"
}
```

## Introduction

Manage your Felt directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.
You can do this in two different ways:
- Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach
- Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control

## Also integrate Felt with

- [OpenAI Agents SDK](https://composio.dev/toolkits/felt/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/felt/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/felt/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/felt/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/felt/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/felt/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/felt/framework/cli)
- [Google ADK](https://composio.dev/toolkits/felt/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/felt/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/felt/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/felt/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/felt/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/felt/framework/crew-ai)

## TL;DR

- Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
- Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
- Handling Large tool responses out of LLM context to minimize context rot.
- Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

## Connect Felt to Claude Code

### Connecting Felt to Claude Code using Composio
1. Add the Composio MCP to Claude

```bash
claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp
```

## What is Claude Code?

Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working.
Key features include:
- Terminal-Native Experience: Work with Claude directly in your command line without switching contexts
- MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities
- Project Context: Claude understands your project structure and can read, write, and modify files
- Interactive Development: Ask questions, debug code, and get help in real-time while coding
- Multi-Platform: Works on macOS, Linux, WSL, and Windows

## What is the Felt MCP server, and what's possible with it?

The Felt MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Felt account. It provides structured and secure access to your maps, projects, and geospatial data, so your agent can perform actions like creating projects, modifying maps, updating map elements, and retrieving user or map details on your behalf.
- Project and map creation: Instantly have your agent create new Felt projects and initialize interactive maps to kickstart geospatial workflows.
- Element and layer management: Direct your agent to add, update, or delete map elements and layers—making it easy to modify map content or clean up unwanted data.
- Map duplication and deletion: Clone existing maps for experimentation or backup, or remove entire maps and projects when they’re no longer needed.
- Detailed map and user insights: Retrieve comprehensive details about any specific map or your authenticated user profile for streamlined map management and reporting.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `FELT_CREATE_OR_UPDATE_ELEMENTS` | Create or Update Elements | Create or update map elements using GeoJSON FeatureCollection format. Creates new elements by default; to update existing elements, include 'felt:id' in the feature's properties. Supports Point, LineString, Polygon, and Multi-type geometries. Returns the created/updated elements with assigned IDs and Felt-specific properties. |
| `FELT_CREATE_PROJECT` | Create Project | Create a new Felt project with the specified name and visibility settings. Projects are organizational containers for grouping related maps within a workspace. |
| `FELT_DELETE_ELEMENT` | Delete Element | Tool to delete a specific element from a map. Use when you have both map and element IDs and need to remove the element permanently. |
| `FELT_DELETE_LAYER` | Delete Layer | Tool to delete a specific layer from a map. Use when you have the map's and layer's IDs and need to remove it permanently. |
| `FELT_DELETE_MAP` | Delete Map | Permanently deletes a map and all its associated data from Felt. WARNING: This action cannot be undone. The map and all its layers, elements, and comments will be permanently removed. Use when you have the map's ID and need to permanently remove it. Returns no content (HTTP 204) on success. |
| `FELT_DELETE_PROJECT` | Delete Project | Tool to delete a project and all its contents. Use when you need to permanently remove a project after confirmation. |
| `FELT_DUPLICATE_MAP` | Duplicate Map | Creates a complete copy of a Felt map including all layers, elements, and configuration. Use when you need to clone an existing map to a new location or create a template-based map. The duplicated map can optionally be placed in a specific project or folder. |
| `FELT_GET_MAP_DETAILS` | Get Map Details | Retrieves comprehensive details of a specific Felt map including title, URL, layers, elements, basemap settings, access permissions, and timestamps. Requires a valid map ID. Use this when you need to: - Get complete map configuration and metadata - Access map layers and elements - Check map permissions and access settings - Retrieve map URLs for sharing |
| `FELT_GET_USER_DETAILS` | Get User Details | Tool to retrieve information about the authenticated user. Use after obtaining a valid token to fetch user profile details. |
| `FELT_LIST_ELEMENT_GROUPS` | List Element Groups | Retrieves all element groups from a Felt map. Element groups are collections of geographic features (points, lines, polygons) organized together. Each group returns a GeoJSON FeatureCollection with the group's elements, along with styling properties like color and symbol. Use this when you need to discover what element groups exist on a map or access grouped geographic data. |
| `FELT_LIST_ELEMENTS` | List Elements | Lists all elements on a specific map as a GeoJSON FeatureCollection. Returns elements that are not in element groups. Use when you need to retrieve the map's direct elements after obtaining a valid map_id. |
| `FELT_LIST_LAYERS` | List Layers | Tool to list all layers on a specific map. Returns all layers present on the map with their complete metadata including status, geometry type, styling, and attributes. Use this when you need to inspect or enumerate the data layers on a map. |
| `FELT_LIST_PROJECTS` | List Projects | Tool to retrieve a list of projects accessible to the user. Use when you need to browse or select from existing projects before proceeding. |
| `FELT_LIST_SOURCES` | List Sources | List all data sources (external data connections) accessible to the authenticated user. Sources represent connections to external data providers like BigQuery, PostgreSQL, S3, Snowflake, etc. Use this to discover available sources before importing data from them into Felt maps. Each source includes sync status, connection type, and access permissions. |
| `FELT_UPDATE_PROJECT` | Update Project | Tool to update an existing project's name or visibility. Use after confirming the project_id. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Felt MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Felt account. It provides structured and secure access so Claude can perform Felt operations on your behalf.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Claude Pro, Max, or API billing enabled Anthropic account
- Composio API Key
- A Felt account
- Basic knowledge of Python or TypeScript

### 1. Install Claude Code

To install Claude Code, use one of the following methods based on your operating system:
```bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
```

### 2. Set up Claude Code

Open a terminal, go to your project folder, and start Claude Code:
- Claude Code will open in your terminal
- Follow the prompts to sign in with your Anthropic account
- Complete the authentication flow
- Once authenticated, you can start using Claude Code
```bash
cd your-project-folder
claude
```

### 3. Set up environment variables

Create a .env file in your project root with the following variables:
- COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code))
- USER_ID identifies the user for session management (use any unique identifier)
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
```

### 4. Install Composio library

No description provided.
```python
pip install composio-core python-dotenv
```

```typescript
npm install @composio/core dotenv
```

### 5. Generate Composio MCP URL

No description provided.
```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["felt"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http felt-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['felt'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http felt-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

### 6. Run the script and copy the MCP URL

No description provided.
```python
python generate_mcp_url.py
```

```typescript
node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts
```

### 7. Add Felt MCP to Claude Code

In your terminal, add the MCP server using the command from the previous step. The command format is:
- claude mcp add registers a new MCP server with Claude Code
- --transport http specifies that this is an HTTP-based MCP server
- The server name (felt-composio) is how you'll reference it
- The URL points to your Composio Tool Router session
- --headers includes your Composio API key for authentication
After running the command, close the current Claude Code session and start a new one for the changes to take effect.
```bash
claude mcp add --transport http felt-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude
```

### 8. Verify the installation

Check that your Felt MCP server is properly configured.
- This command lists all MCP servers registered with Claude Code
- You should see your felt-composio entry in the list
- This confirms that Claude Code can now access Felt tools
If everything is wired up, you should see your felt-composio entry listed:
```bash
claude mcp list
```

### 9. Authenticate Felt

The first time you try to use Felt tools, you'll be prompted to authenticate.
- Claude Code will detect that you need to authenticate with Felt
- It will show you an authentication link
- Open the link in your browser (or copy/paste it)
- Complete the Felt authorization flow
- Return to the terminal and start using Felt through Claude Code
Once authenticated, you can ask Claude Code to perform Felt operations in natural language. For example:
- "Add geojson features to an existing map"
- "Duplicate a project map for a new client"
- "Delete a layer from my city zoning map"

## Complete Code

```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["felt"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http felt-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['felt'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http felt-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

## Conclusion

You've successfully integrated Felt with Claude Code using Composio's MCP server. Now you can interact with Felt directly from your terminal using natural language commands.
Key features of this setup:
- Terminal-native experience without switching contexts
- Natural language commands for Felt operations
- Secure authentication through Composio's managed MCP
- Tool Router for dynamic tool discovery and execution
Next steps:
- Try asking Claude Code to perform various Felt operations
- Add more toolkits to your Tool Router session for multi-app workflows
- Integrate this setup into your development workflow for increased productivity
You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

## How to build Felt MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/felt/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/felt/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/felt/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/felt/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/felt/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/felt/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/felt/framework/cli)
- [Google ADK](https://composio.dev/toolkits/felt/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/felt/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/felt/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/felt/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/felt/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/felt/framework/crew-ai)

## Related Toolkits

- [Excel](https://composio.dev/toolkits/excel) - Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management.
- [21risk](https://composio.dev/toolkits/_21risk) - 21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters.
- [Abstract](https://composio.dev/toolkits/abstract) - Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions.
- [Ambee](https://composio.dev/toolkits/ambee) - Ambee is an environmental data platform providing real-time, hyperlocal APIs for air quality, weather, and pollen. Get precise environmental insights to power smarter decisions in your apps and workflows.
- [Ambient weather](https://composio.dev/toolkits/ambient_weather) - Ambient Weather is a platform for personal weather stations with a robust API for accessing local, real-time, and historical weather data. Get detailed environmental insights directly from your own sensors for smarter apps and automations.
- [Anonyflow](https://composio.dev/toolkits/anonyflow) - Anonyflow is a service for encryption-based data anonymization and secure data sharing. It helps organizations meet GDPR, CCPA, and HIPAA data privacy compliance requirements.
- [Api ninjas](https://composio.dev/toolkits/api_ninjas) - Api ninjas offers 120+ public APIs spanning categories like weather, finance, sports, and more. Developers use it to supercharge apps with real-time data and actionable endpoints.
- [Api sports](https://composio.dev/toolkits/api_sports) - Api sports is a comprehensive sports data platform covering 2,000+ competitions with live scores and 15+ years of stats. Instantly access up-to-date sports information for analysis, apps, or chatbots.
- [Apify](https://composio.dev/toolkits/apify) - Apify is a cloud platform for building, deploying, and managing web scraping and automation tools called Actors. It lets you automate data extraction and workflow tasks at scale—no infrastructure headaches.
- [Autom](https://composio.dev/toolkits/autom) - Autom is a lightning-fast search engine results data platform for Google, Bing, and Brave. Developers use it to access fresh, low-latency SERP data on demand.
- [Beaconchain](https://composio.dev/toolkits/beaconchain) - Beaconchain is a real-time analytics platform for Ethereum 2.0's Beacon Chain. It provides detailed insights into validators, blocks, and overall network performance.
- [Big data cloud](https://composio.dev/toolkits/big_data_cloud) - BigDataCloud provides APIs for geolocation, reverse geocoding, and address validation. Instantly access reliable location intelligence to enhance your applications and workflows.
- [Bigpicture io](https://composio.dev/toolkits/bigpicture_io) - BigPicture.io offers APIs for accessing detailed company and profile data. Instantly enrich your applications with up-to-date insights on 20M+ businesses.
- [Bitquery](https://composio.dev/toolkits/bitquery) - Bitquery is a blockchain data platform offering indexed, real-time, and historical data from 40+ blockchains via GraphQL APIs. Get unified, reliable access to complex on-chain data for analytics, trading, and research.
- [Brightdata](https://composio.dev/toolkits/brightdata) - Brightdata is a leading web data platform offering advanced scraping, SERP APIs, and anti-bot tools. It lets you collect public web data at scale, bypassing blocks and friction.
- [Builtwith](https://composio.dev/toolkits/builtwith) - BuiltWith is a web technology profiler that uncovers the technologies powering any website. Gain actionable insights into analytics, hosting, and content management stacks for smarter research and lead generation.
- [Byteforms](https://composio.dev/toolkits/byteforms) - Byteforms is an all-in-one platform for creating forms, managing submissions, and integrating data. It streamlines workflows by centralizing form data collection and automation.
- [Cabinpanda](https://composio.dev/toolkits/cabinpanda) - Cabinpanda is a data collection platform for building and managing online forms. It helps streamline how you gather, organize, and analyze responses.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Felt MCP?

With a standalone Felt MCP server, the agents and LLMs can only access a fixed set of Felt tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Felt and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Felt tools.

### Can I manage the permissions and scopes for Felt while using Tool Router?

Yes, absolutely. You can configure which Felt scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Felt data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
