Skip to main content
Glama
YawLabs

@yawlabs/tailscale-mcp

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create OAuth app

tailscale_create_oauth_app

Create an OAuth app to let a third-party service enroll devices into your tailnet. Uses the authorization-code flow after user consent and returns the client secret for immediate saving.

Instructions

Create an OAuth App for device provisioning (Tailscale alpha). Lets a third-party application enroll a device into your tailnet via the authorization-code flow, after a user consents. Returns the app's client secret -- save it immediately, it cannot be retrieved again.

SECURITY: the response body contains a long-lived credential verbatim. MCP clients commonly persist tool responses to logs and conversation transcripts; treat this response as sensitive.

Use scope 'auth_keys:create:once' (one auth key per authorization, no refresh token) -- the scope Tailscale's device-provisioning guide documents. The API reference's example shows 'auth_keys:create'; this tool does not restrict the value. Distinct from tailscale_create_key with keyType='client', which mints a machine-to-machine OAuth client instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesHuman-readable name for the OAuth app, shown on the consent screen
scopesYesScopes to grant. Use 'auth_keys:create:once', the scope the device-provisioning guide documents; the API reference's example shows 'auth_keys:create'. Not restricted here.
redirectUrisYesAllowed redirect URIs for the authorization-code flow (e.g. ['https://example.com/callback'])
allowedNodeAttributesNoOptional node attributes the app may request when provisioning a device

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.21.0
    • changedInput schema / properties / scopes / description
      Previous value: -"Scopes to grant. Currently 'auth_keys:create:once' is the supported value."New value: +"Scopes to grant. Use 'auth_keys:create:once', the scope the device-provisioning guide documents; the API reference's example shows 'auth_keys:create'. Not restricted here."
  2. Addedv0.17.1

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds important behavior beyond annotations: the response contains a long-lived credential that cannot be retrieved again, and MCP clients may persist it in logs. The security warning and alpha status give the agent operational context that readOnlyHint/idempotentHint/destructiveHint do not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core function and flow, then handles security, scope guidance, and sibling differentiation. Every paragraph serves a distinct purpose and no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the moderate complexity and lack of an output schema, the description covers purpose, flow, required parameters, secret handling, and the key sibling alternative. The agent has enough information to invoke the tool correctly and handle its response safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining the recommended scope's semantics ('one auth key per authorization, no refresh token') and clarifying that the tool does not restrict the scope value despite the API reference's example.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States it creates an OAuth app for device provisioning, describes the authorization-code flow and user consent, and notes it returns the client secret. It also distinguishes itself from tailscale_create_key, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names tailscale_create_key with keyType='client' as the alternative for machine-to-machine OAuth clients, and frames this tool as the one for third-party device enrollment after user consent. It also recommends the exact scope to use, leaving little room for incorrect selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools