Manage Your Tailscale Network Through Your Muse

Through an AnythingMCP custom connector, your muse can run the admin side of your Tailscale network in plain words: list devices, check who can reach what, and test an access-rule change before it goes live.

What it does

The connector adds 46 tools for a Tailscale network, called a tailnet. Your muse can list devices with names, owners, and tags, approve a waiting device, and set its tags or name. It can list users by role, approve or suspend one, and restore a suspended one. It can list keys without showing their values and create a new auth key to add a server, valid for at most 90 days. It can read the policy file holding the access rules, check a draft, and preview which rules would hit one user, saving nothing. It can read DNS settings, the audit log of who changed what in the last 90 days, and network flow logs. Deleting devices, users, or keys, and replacing the policy file, are switched off at install.

How to use it

1. You need a tailnet user with the Owner, Admin, Network admin, or IT admin role.
2. In the Tailscale admin console, open Settings, then Trust credentials, and create an OAuth client. For reading only, the all:read scope suffices.
3. Copy the client ID and client secret, shown once, into the connector fields in AnythingMCP. An ordinary API token does not work here.
4. In Muse, open Settings, then Connectors, and add a custom connector with the address AnythingMCP gives you. Sign in and approve.
5. Start with a read: ask for the list of devices. Before any change, ask the muse to show the current and new values side by side.

What you need

• A Muse account that can add custom connectors
• An AnythingMCP account with the Tailscale connector added
• A Tailscale tailnet and an OAuth client created by an admin

What to watch for

• Changes to routes, tags, nameservers, and search paths replace the whole list, so a value left out is removed. The muse should read the current list first and send it back with the new entry.
• A new auth key and a new webhook secret appear in the chat and are shown only once. Treat them like passwords and store them at once.
• Renaming a device changes its MagicDNS name at once, and links that use the old name stop working.
• This is a custom connector, and Meta does not review custom connectors. You can disconnect it in Settings at any time. The muse prepares, you decide.