Intuiface MCP integration for AI agents.
Connect AI agents to Intuiface through 2 structured actions, including list available experiences and send message. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 2
- 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 Intuiface integration exposes
The Intuiface Agent App exposes 2 provider-backed actions for communication and design & media work. Its current contract lets an authorized agent list running intuiface experiences that can receive web trigger messages and send a web trigger message to selected running intuiface experiences. 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 Intuiface account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Intuiface capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_available_experiencesREADList running Intuiface experiences that can receive Web Trigger messages.
INPUTS: experienceNames / experienceIDs / playerDeviceNames / playerIDs / playerTags
send_messageWRITESend a Web Trigger message to selected running Intuiface experiences.
INPUTS: message / parameter1 / parameter2 / parameter3 / experienceNames
INPUT CONTRACTS
Know what the action needs before it runs.
list_available_experiences
experienceNamesOPTIONAL- Experience names that must exactly match running Intuiface experiences.
experienceIDsOPTIONAL- Experience IDs that must exactly match running Intuiface experiences.
playerDeviceNamesOPTIONAL- Player device names that must exactly match Players running the experiences.
playerIDsOPTIONAL- Player IDs that must exactly match Players running the experiences.
playerTagsOPTIONAL- Player tags used to select Players with one or more matching tags.
send_message
messageREQUIRED- The message value sent to every selected experience.
parameter1OPTIONAL- The first optional value sent with the message.
parameter2OPTIONAL- The second optional value sent with the message.
parameter3OPTIONAL- The third optional value sent with the message.
experienceNamesOPTIONAL- Experience names that must exactly match running Intuiface experiences.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Available Experiences
List running Intuiface experiences that can receive Web Trigger messages. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_available_experiencesControl Send Message
Send a Web Trigger message to selected running Intuiface experiences. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
send_messageVerify with Send Message
Send a Web Trigger message to selected running Intuiface experiences. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
send_messageSAFETY BOUNDARY
Operate Intuiface with explicit limits
- Authorize Intuiface with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Intuiface rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Intuiface task completed successfully.
CONNECTION MODEL
API key
Intuiface Credential Key with the Web Triggers scope, sent in the x-api-key header. Create or manage keys on the official Credential Keys page: https://my.intuiface.com/credentialkeys?scope=API_WebTriggers.
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
- 1
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
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 Intuiface.