Link multiple pug ASTs together using include/extends
Link multiple pug ASTs together using include/extends. The pug mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.
Professionally supported pug is now available
pug on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Everything the assistant can do here goes through one of these:
Package — The Package tool exposed by this serverOptions — The Options tool exposed by this serverThis sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Pug's toolset — Package, Options — is a fair guide to whether it matches your workflow. It is maintained by pug-bot; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Package | The Package tool exposed by this server. |
| Options | The Options tool exposed by this server. |
{
"mcpServers": {
"linker": {
"command": "npx",
"args": ["-y", "pug"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.