Felt MCP integration for AI agents.
Connect AI agents to Felt through 12 structured actions, including get current user, create map, delete map, and duplicate map. Review authentication, inputs…
- ACTION CONTRACTS
- 12
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Felt integration exposes
The Felt Agent App exposes 12 provider-backed actions for developer tools and productivity work. Its current contract lets an authorized agent get the felt user profile for the authenticated api token, create a felt map with optional initial metadata, and delete one felt map by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Felt account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Felt capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_userREADGet the Felt user profile for the authenticated API token.
create_mapWRITECreate a Felt map with optional initial metadata.
INPUTS: title / description / public_access / basemap / lat
delete_mapHIGH IMPACTDelete one Felt map by ID.
INPUTS: map_id
duplicate_mapREVIEWDuplicate a Felt map, optionally into another project or folder.
INPUTS: map_id / title / destination
create_projectWRITECreate a Felt project in the authenticated workspace.
INPUTS: name / visibility / max_inherited_permission
delete_projectHIGH IMPACTDelete one Felt project by ID.
INPUTS: project_id
get_mapREADGet one Felt map by ID.
INPUTS: map_id
get_projectREADGet one Felt project by ID.
INPUTS: project_id
list_projectsREADList Felt projects accessible to the authenticated user.
INPUTS: workspace_id
move_mapWRITEMove a Felt map to another project or folder in the same workspace.
update_mapWRITEUpdate Felt map metadata and sharing settings.
INPUTS: map_id / title / description / public_access / basemap
update_projectWRITEUpdate Felt project properties.
INPUTS: project_id / name / visibility / max_inherited_permission
INPUT CONTRACTS
Know what the action needs before it runs.
create_map
titleOPTIONAL- The Felt map title.
descriptionOPTIONAL- The Felt map description.
public_accessOPTIONAL- The Felt map public access setting.
basemapOPTIONAL- The Felt basemap identifier.
latOPTIONAL- The initial map center latitude.
delete_map
map_idOPTIONAL- The Felt resource ID.
duplicate_map
map_idREQUIRED- The Felt resource ID.
titleOPTIONAL- The title for the duplicated map.
destinationOPTIONAL- The destination project or folder for a Felt map.
create_project
nameREQUIRED- The name to use for the Felt project.
visibilityREQUIRED- The Felt project visibility setting.
max_inherited_permissionOPTIONAL- The maximum permission level workspace members inherit on team-visible projects.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current User
Get the Felt user profile for the authenticated API token. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_userControl Create Map
Create a Felt map with optional initial metadata. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_mapVerify with Get Map
Get one Felt map by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_mapSAFETY BOUNDARY
Operate Felt with explicit limits
- Authorize Felt with API key and grant only the provider access required by the selected actions.
- 7 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_map` and `delete_project` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Felt rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Felt task completed successfully.
CONNECTION MODEL
API key
Felt API token sent as a Bearer token. Create or view tokens in the Developers tab of Felt Workspace Settings: https://felt.com/maps/latest/developers
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 5
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Felt.