Skip to main content
Glama
YawLabs

@yawlabs/tailscale-mcp

by YawLabs

tailscale_create_key

Create auth keys, OAuth clients, or federated identities for your tailnet. Supports devices, API access, and OIDC-based CI/CD. Save the returned value immediately.

Instructions

Create a new key in your tailnet. Supports auth keys (for adding devices), OAuth clients (for programmatic API access), and federated identities (for OIDC-based CI/CD access). Returns the key value — save it immediately, as 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 (do not commit it, avoid re-sharing it in unrelated chat history).

Examples:

  • Auth key: {keyType:'auth', reusable:true, tags:['tag:ci']}

  • OAuth client: {keyType:'client', scopes:['devices:read','dns']}

  • Federated (GitHub Actions): {keyType:'federated', scopes:['devices:read'], issuer:'https://token.actions.githubusercontent.com', subject:'repo:my-org/my-repo:*'}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoACL tags (must start with 'tag:'). Required for client/federated if scopes include 'devices:core' or 'auth_keys'
issuerNo(federated only) OIDC issuer URL (e.g. 'https://token.actions.githubusercontent.com')
scopesNo(client/federated) OAuth scopes to grant (e.g. ['devices:read', 'dns', 'acl'])
keyTypeNoKey type: 'auth' (default) for device auth keys, 'client' for OAuth clients, 'federated' for OIDC federation
subjectNo(federated only) Expected subject claim, supports * wildcards
audienceNo(federated only) Expected audience claim
reusableNo(auth only) Whether the key can be used more than once (default: false)
ephemeralNo(auth only) Whether devices using this key are ephemeral (default: false)
descriptionNoDescription for this key (max 50 chars, alphanumeric/hyphens/spaces)
expirySecondsNo(auth only) Key expiry in seconds (default: 90 days)
preauthorizedNo(auth only) Whether devices are pre-authorized (default: false)
customClaimRulesNo(federated only) Custom claim mapping rules
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description warns that the key value is returned once and cannot be retrieved again, alerts about sensitive credential persistence in logs, and advises immediate saving. No contradictions with annotations.

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

Conciseness4/5

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

The description is well-structured with purpose, security note, and examples. While it is slightly lengthy, every sentence adds value; the front-loading of purpose and immediate security warning is effective.

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

Completeness4/5

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

Given 12 parameters and no output schema, the description covers the key types, security, and return value (key must be saved). It lacks detail on the full response structure but is adequate for a key-creation tool.

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?

With 100% schema coverage, the description adds value by providing concrete examples for each key type, showing how parameters combine (e.g., federated with issuer and subject), which clarifies usage beyond the schema alone.

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?

The description clearly states 'Create a new key in your tailnet' and lists three distinct types (auth, OAuth, federated), differentiating it from sibling tools like tailscale_list_keys and tailscale_get_key which are read-only operations.

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

Usage Guidelines4/5

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

The description provides clear guidance on when to use each key type with examples, but does not explicitly compare to update/delete siblings or specify when not to use the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YawLabs/tailscale-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server