Tailscale MCP integration for AI agents.
Connect AI agents to Tailscale through 82 structured actions, including get aws external id, approve user, delete device, and expire device key. Review authe…
- ACTION CONTRACTS
- 82
- AUTHENTICATION
- Custom credentials
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Tailscale integration exposes
The Tailscale Agent App exposes 82 provider-backed actions for security and developer tools work. Its current contract lets an authorized agent create or retrieve the aws external id used by tailscale log streaming, approve a pending tailscale user for the tailnet, and permanently delete a device from its tailscale tailnet. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses Custom credentials. 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 Tailscale account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Tailscale capabilities.
Showing 12 of 82 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_aws_external_idREADCreate or retrieve the AWS external ID used by Tailscale log streaming.
INPUTS: reusable
approve_userWRITEApprove a pending Tailscale user for the tailnet.
INPUTS: userId
delete_deviceHIGH IMPACTPermanently delete a device from its Tailscale tailnet.
INPUTS: deviceId
expire_device_keyREVIEWImmediately expire a device key and require the device to authenticate again.
INPUTS: deviceId
batch_update_device_posture_attributesWRITESet or remove custom posture attributes across multiple Tailscale devices.
INPUTS: nodes / comment
create_keyWRITECreate an auth key, OAuth client credential, or federated trust credential and return its secret.
INPUTS: key
create_oauth_appWRITECreate a Tailscale OAuth application and return its client secret.
INPUTS: app
create_posture_integrationWRITECreate a device posture integration using its external provider credentials.
INPUTS: integration
create_webhookWRITECreate a webhook endpoint and return its signing secret.
INPUTS: webhook
delete_device_inviteHIGH IMPACTDelete a Tailscale device share invite.
INPUTS: deviceInviteId
delete_device_posture_attributeHIGH IMPACTPermanently remove one custom posture attribute from a Tailscale device.
INPUTS: deviceId / attributeKey
delete_keyHIGH IMPACTPermanently revoke and delete a Tailscale trust credential or key.
INPUTS: keyId
INPUT CONTRACTS
Know what the action needs before it runs.
get_aws_external_id
reusableOPTIONAL- Whether later reusable calls may receive this same external ID, until it is linked with an AWS account.
approve_user
userIdREQUIRED- The pending Tailscale user ID.
delete_device
deviceIdREQUIRED- The preferred nodeId or legacy id of the device to delete.
expire_device_key
deviceIdREQUIRED- The preferred nodeId or legacy id of the device.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Aws External Id
Create or retrieve the AWS external ID used by Tailscale log streaming. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_aws_external_idControl Approve User
Approve a pending Tailscale user for the tailnet. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
approve_userVerify with Approve User
Approve a pending Tailscale user for the tailnet. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
approve_userSAFETY BOUNDARY
Operate Tailscale with explicit limits
- Authorize Tailscale with Custom credentials and grant only the provider access required by the selected actions.
- 40 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_device`, `delete_device_invite`, and `delete_device_posture_attribute` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `users`, `devices:posture_attributes`, `auth_keys`, and `oauth_keys`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Tailscale task completed successfully.
CONNECTION MODEL
Custom credentials
Tailscale uses Custom credentials. Connection requirements and availability are determined by the provider and the Working Machines deployment.
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
- 35
- WRITE SIGNALS
- 30
- HIGH IMPACT
- 10
- REVIEW SIGNALS
- 7
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 Tailscale.