Ashlr Stack — the control plane for your entire dev stack. Provisions, wires, and operates every service in your project with one command.
Ashlr Stack MCP server exists for a simple reason — assistants are far more useful when they can act on Ashlr Stack directly instead of describing what you should do. Ashlr Stack — the control plane for your entire dev stack. Provisions, wires, and operates every service in your project with one command.
In a Claude‑Code‑native world, the friction in starting a project isn't writing code — it's tab‑hopping to create and wire ten services. Every npx create-next-app is followed by an hour of:
Once Ashlr Stack is connected, these are the calls the assistant has available:
Publishing — Three packages ship to npm: @ashlr/stack-core, ashlr-stack-mcp, @ashlr/stack. For monorepo dev, @ashlr/stack depends on @ashlr/stack-core viaThe server ships on npm as create-next-app, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Ashlr Stack's toolset — Publishing — is a fair guide to whether it matches your workflow. It is maintained by ashlrai; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Ashlr Stack's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Publishing | Three packages ship to npm: @ashlr/stack-core, ashlr-stack-mcp, @ashlr/stack. For monorepo dev, @ashlr/stack depends on @ashlr/stack-core via workspace:* — that's what lets bun install link the local checkout. A plain np |
{
"mcpServers": {
"ashlr-stack": {
"command": "npx",
"args": ["-y", "create-next-app"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.