Use Felt from Claude
Add the Felt connection to a Space that runs Claude, then use it from every channel in that Space.
Connect Felt once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Felt connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Felt connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Felt is a mapping tool for building and sharing interactive maps, with layers, elements, and projects organized in a workspace. Teams that connect Felt to type.com can ask Claude to add shapes to a map, start a new project, or tidy up old layers, with the result visible to everyone in the Space.
Connect Felt once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Hand the agent a list of addresses or coordinates and have it place them as elements on a Felt map for the team to review.
Add these 40 store locations as points on our Felt map and label each with its city.
Spin up a fresh Felt project with the right visibility setting so a new mapping effort has a home before anyone starts adding layers.
Create a private Felt project called Q4 Site Survey for the field team.
Remove old elements, layers, or maps that are no longer needed, so the workspace does not fill up with abandoned drafts.
Delete the three test layers we added to the warehouse map last week.
Adds shapes, points, or lines to a map from location data, or edits ones that already exist.
Starts a new Felt project to group related maps together under one workspace folder.
Removes one shape or marker from a map once its identifier is known.
Removes an entire layer of data from a map, such as a batch of imported points.
Permanently removes a map along with its layers and comments, so use it only for maps nobody needs.
Felt provides GIS developer tools for creating, managing, embedding, and controlling maps. REST APIs support maps, layers, elements, projects, folders, and map duplication/movement with Bearer-token authentication; SDKs support embedded interactive map experiences and geospatial app development.
Yes. With a Felt connection shared into a type.com Space, Claude can add or update elements, start new projects, and clean up old layers or maps from a thread, and the team sees the same result inside Felt.
Felt uses an API key. An admin adds it once when setting up the connection, then picks which Spaces can use it, so nobody has to paste a key into a prompt.
Yes. A prompt like removing an old layer each month can be saved as a type.com automation that runs on that schedule and posts a summary to a channel.
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Connect Mercury MCP to Claude in type.com to check account balances, review transactions, and pull statements without touching the Mercury dashboard.
Connect Mezmo to Claude in type.com to create exclusion rules, provision API keys, and set up log alerts from a shared thread.
Connect Minerstat to Claude in type.com to check offline workers, compare mining hardware, and pull pool fees right inside a thread.
Connect Mistral AI to Claude in type.com to run chat completions, transcribe audio, and configure custom agents from a shared dev thread.