Envoy MCP integration for AI agents.
Connect AI agents to Envoy through 8 structured actions, including get employee, get flow, and get invite. Review authentication, inputs, workflows, and safe…
- ACTION CONTRACTS
- 8
- 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 Envoy integration exposes
The Envoy Agent App exposes 8 provider-backed actions for productivity and security work. Its current contract lets an authorized agent fetch one envoy employee by id, fetch one envoy sign-in flow by id, and fetch one envoy invite 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 Envoy account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Envoy capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_employeeREADFetch one Envoy employee by ID.
INPUTS: id
get_flowREADFetch one Envoy sign-in flow by ID.
INPUTS: id
get_inviteREADFetch one Envoy invite by ID.
INPUTS: id
get_locationREADFetch one Envoy location by ID.
INPUTS: id
list_employeesREADList Envoy employees with optional search filters and pagination.
INPUTS: ids / page / perPage / order / name
list_flowsREADList Envoy sign-in flows with optional filters and pagination.
INPUTS: ids / page / perPage / order / locationIds
list_invitesREADList Envoy invites with optional filters and pagination.
INPUTS: ids / page / perPage / order / locationIds
list_locationsREADList Envoy locations with optional filters and pagination.
INPUTS: ids / page / perPage / order / createdAtAfter
INPUT CONTRACTS
Know what the action needs before it runs.
get_employee
idREQUIRED- The Envoy resource ID.
get_flow
idREQUIRED- The Envoy resource ID.
get_invite
idREQUIRED- The Envoy resource ID.
get_location
idREQUIRED- The Envoy resource ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Employee
Fetch one Envoy employee by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_employeeVerify with Get Flow
Fetch one Envoy sign-in flow by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_flowSAFETY BOUNDARY
Operate Envoy with explicit limits
- Authorize Envoy with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Envoy data may still be sensitive and should be minimized before it enters model context.
- 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 Envoy rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Envoy task completed successfully.
CONNECTION MODEL
API key
Envoy Client API Key sent in the X-API-Key header for private apps. Create a private app and generate a Client API Key in the Envoy dashboard: https://developers.envoy.com/hub/docs/client-api-keys.
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
- 8
- WRITE SIGNALS
- 0
- 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 Envoy.