Derive vs Tailscale MCP Server
A side-by-side look at the Derive and Tailscale MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Derive for developer tools work as a local process; choose Tailscale MCP Server for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Derive when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DERIVE_SERVER, DERIVE_TOKEN. - You want tools like
list_workspaces, list_artifacts, search.
Choose Tailscale MCP Server when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TAILSCALE_API_KEY. - You want tools like
tailscale_tool_groups, tailscale_status, tailscale_list_devices.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 64/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | DERIVE_SERVERDERIVE_TOKEN | TAILSCALE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 30 | 34 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 8 | 98 |
| Full listing | View Derive | View Tailscale MCP Server |
Tools & capabilities
Derive tools 8
list_workspacesList every workspace signed in on this machine you can act in — id, name, your role, local description, and which is active. One login reaches them all; pass a workspace's id or name as the `workspace` argument to list_artifacts / read / catch_up / comment / publish to act there for that call.list_artifactsList the artifacts in your workspace — short id, title, kind, current version, access, and browse `tags`. Defaults to this session's workspace; pass `workspace` (id or name from list_workspaces) to list another. Pass `tag` to list only artifacts carrying that tag (organize shows the vocabulary). Start here to find what to work on, then catch_up or read it.searchFind text within ONE artifact, or across a WORKSPACE — same tool, same behavior as the remote MCP server's `search`. Pass short_id to grep one artifact: matching lines with line numbers (and optional context), ripgrep-style, so you can then `read` a narrow `lines` range or `edit` that spot. Omit short_id to search across the workspace — the artifacts you can see, ranked by relevance and grouped by artifact — find WHICH doc has something before opening it. Searches the exact source by default (in:'text' searches the visible text instead). The query is matched literally (metacharacters are not special).readRead an artifact's CONTENT by short id, as Markdown by default (HTML is converted). Omit `section` to see the outline first (heading slugs for a single-file doc, page paths for a bundle) — call again with a `section` (or "*" for the full document) once you know what you want. Pass `format:'html'` for the exact source (needed before publish `edits`), or a past `version` for history. Also accepts derive://guide, /connect, or /compatibility so the onboarding strings in server instructions work even when MCP resources do not. For what CHANGED or the comment threads, use catch_up instead.catch_upSTART HERE on an artifact. Its state in one call: a summary, the review round, the versions since `since_version`, the open (and outdated) comment threads, and the full version history. Pass `comments` (open / addressed / resolved / outdated) to instead get that filtered thread list — your feedback queue. Pass `response_format='detailed'` (optionally with `since_version`/`to_version`) to fold in a line diff between two versions — of their readable Markdown form, not raw HTML. WAITING ON A REVIEW? Pass `wait` (seconds, max 50) to block until the human sends back — chain these instead of sleeping between polls.commentLeave feedback, reply in a thread, react, and/or resolve or reopen a thread. Anchor a NEW comment to text with `quote`, or to a linked-bundle loop/graph part with `visual_target`. Reply by passing the thread id as `reply_to`.organizeTags and collections in one tool — the library's findability layer. • READ (no `short_ids`): the workspace's tag vocabulary (tag → count) and its collections. Call this before tagging to reuse an existing tag over a near-duplicate. • READ (with `short_ids`): those artifacts' current tags + collections, plus `suggested` tags drawn from the most semantically-similar docs (when one id is given). • WRITE: pass `add`/`remove`/`set` to change tags, `collection` to file artifacts, or `state:'archived'`/`'live'` to archive and restore. Each artifact is authorized on its own; ones you can't touch are skipped. Tag freely and reuse the vocabulary — a well-tagged library is findable. Collections are heavier: a tag for plain findability, a collection when a set is a real unit.publishPublish a single-file artifact and get a permanent URL, versions, and feedback (a chat-local artifact has none of these). OMIT short_id to create a NEW artifact (title recommended); PASS short_id to publish a new version (same URL). Provide the body as `content_path` (a local file this server reads and uploads — preferred, zero tokens) or `content` (inline text). To CHANGE PART of an existing artifact, prefer `edits` (exact-match search/replace against the stored source — read format:'html' first) over resending everything. Pass `addresses` with the thread ids this revision resolves. (Multi-page bundles are published via the web app or the remote /mcp server.) FULLY-STYLED HTML renders as-authored (own <style>/scripts/fonts) in the sandboxed viewer — declare your own <meta name="viewport"> to skip the mobile-reflow injection, and self-host binaries via POST /v1/assets (images and woff2 fonts) instead of inlining base64.
Tailscale MCP Server tools 98
tailscale_tool_groupsExplain which of this server's tools are available and why. Call this FIRST when a Tailscale tool you expected is missing, instead of assuming the capability does not exist -- tools can be withheld by configuration, and the fix is usually one environment variable. Pass `toolName` to ask about one specific tool (e.g. 'tailscale_delete_device'): the answer distinguishes 'no such tool exists' -- where you should find another approach -- from 'it exists but its group is not loaded' and 'it exists and loaded but writes are withheld there', both of which the operator can enable and neither of which you should work around. With no arguments it lists every group with its availability and, where something is withheld, the exact environment change that would restore it. Always available regardless of filters.tailscale_statusCheck that the Tailscale API connection is working. Returns your tailnet name, device count, and confirms authentication is valid. Use this to verify setup.tailscale_list_devicesList all devices in your tailnet with their status, IP addresses, OS, and last seen time. 'lastSeen' is omitted while a device is connected (connectedToControl: true) and for devices that have never been online -- on a connected device a missing lastSeen means online now, not never seen.tailscale_get_deviceGet detailed information about a specific device by its ID. Returns the default field subset unless fields: 'all'. 'lastSeen' is omitted while a device is connected (connectedToControl: true) and for devices that have never been online -- on a connected device a missing lastSeen means online now, not never seen.tailscale_authorize_deviceAuthorize a device that is pending authorization.tailscale_deauthorize_deviceDeauthorize a device, immediately removing its access to the tailnet. The device will need to be re-authorized to reconnect.tailscale_delete_devicePermanently remove a device from the tailnet. This is irreversible -- the device must re-authenticate to rejoin.tailscale_rename_deviceSet the name of a device in the tailnet, or reset it to its OS hostname.tailscale_expire_deviceExpire a device's key, forcing it to re-authenticate.tailscale_get_device_routesGet the subnet routes a device advertises and which are enabled.tailscale_set_device_routesSet the enabled subnet routes for a device. Replaces all currently enabled routes -- pass the full list of routes you want enabled.tailscale_get_device_posture_attributesGet all posture attributes for a device, including custom and system-managed attributes.- +86 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Derive
{
"mcpServers": {
"derive": {
"command": "npx",
"args": [
"-y",
"@derive-to/mcp"
],
"env": {
"DERIVE_SERVER": "YOUR_DERIVE_SERVER_HERE",
"DERIVE_TOKEN": "YOUR_DERIVE_TOKEN_HERE"
}
}
}
}
Tailscale MCP Server
{
"mcpServers": {
"tailscale-mcp-server-2": {
"command": "npx",
"args": [
"-y",
"@yawlabs/tailscale-mcp@latest"
],
"env": {
"TAILSCALE_API_KEY": "YOUR_TAILSCALE_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Derive is categorized under Developer Tools and uses a local stdio subprocess. Tailscale MCP Server belongs to Developer Tools and uses a local stdio subprocess. Pick Derive for developer tools work and Tailscale MCP Server for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Derive has no declared pricing — check the project's own site. Tailscale MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add derive and tailscale-mcp-server-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Derive has a quality signal of 64/100 (Good) with 0 views, 0 installs and 30 GitHub stars. Tailscale MCP Server has 64/100 (Good) with 0 views, 0 installs and 34 GitHub stars.