How to connect Felt to OpenClaw
Connect Felt to OpenClaw with ClawLink: paste your Felt key once and 15 tools work from chat. No MCP server to run, nothing stored on your machine.
FeltAPI KEYMCPFelt is a modern GIS platform that allows users to create, modify, and share interactive maps, integrating powerful mapping capabilities into various workflows and applications.. Once connected, OpenClaw can read and act on Felt from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Felt access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Felt setup: install one ClawHub skill, connect Felt in the browser, and OpenClaw can call real Felt actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Felt.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Felt
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Felt?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Felt in the ClawLink dashboard — paste your Felt API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Felt, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Felt is connected in the dashboard, that agent calls the same 15 Felt tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Felt MCP for OpenClaw
Looking for a Felt MCP server for OpenClaw? ClawLink connects Felt to OpenClaw and exposes 15 Felt tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Felt integration works the same way.
What the OpenClaw Felt integration can do
15 Felt tools are ready for OpenClaw once the account is connected. The 11 below are the ones people reach for most; your agent can call all 15.
11 of 15 Felt tools for OpenClaw
| Tool | What it does |
|---|---|
Get map details felt_get_map_details | Retrieves comprehensive details of a specific Felt map including title, URL, layers, elements |
Get user details felt_get_user_details | Retrieve information about the authenticated user |
List element groups felt_list_element_groups | Retrieves all element groups from a Felt map |
List elements felt_list_elements | Lists all elements on a specific map as a GeoJSON FeatureCollection |
List layers felt_list_layers | List all layers on a specific map |
List projects felt_list_projects | Retrieve a list of projects accessible to the user |
List sources felt_list_sources | List all data sources (external data connections) accessible to the authenticated user |
Create or update elements felt_create_or_update_elements | Create or update map elements using GeoJSON FeatureCollection format |
Create project felt_create_project | Create a new Felt project with the specified name and visibility settings |
Duplicate map felt_duplicate_map | Creates a complete copy of a Felt map including all layers, elements, and configuration |
Update project felt_update_project | Update an existing project's name or visibility |
Try it: find the Felt tool you need
Browse the 11 Felt tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Felt, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Felt, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Felt, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Felt, group them by priority, and recommend what OpenClaw should do next.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Felt working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Felt API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Felt account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Felt. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Felt actions to the runtime in a format your agent can reliably use. | 15 tools for Felt are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Felt to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Felt in the browser, and the 15 tools above work from chat. There is no SDK and no config file, and the Felt key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Felt skill but can't call the tools
The ClawHub skill teaches OpenClaw about Felt, but the calls run through the ClawLink plugin and your connected account. Make sure Felt is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Felt from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Felt tools
Felt tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Felt call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Felt returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Felt has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Felt integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Felt: link your Felt account once in the browser and OpenClaw can call the Felt API through 15 ready-made tools — no custom code or token handling.
How do I add Felt to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Felt skill from ClawHub, then you click Connect in the dashboard to authorize Felt. OpenClaw calls the tools from the next message — no config files, and the Felt key you paste is stored server-side instead of in your environment.
How long does it take to connect Felt to OpenClaw?
About two minutes. Sign in, click Connect next to Felt in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Felt up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Felt working from chat.
OpenClaw installed the Felt skill but can't call the tools
The ClawHub skill teaches OpenClaw about Felt, but the calls run through the ClawLink plugin and your connected account. Make sure Felt is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
GitHub
Manage repositories, issues, pull requests, and workflows
Connect PagerDuty
Manage incidents, on-call schedules, and services
SafetyCulture tools
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.