ashlr-stack-mcp 0.3.0 → 0.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +3 -3
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -1,10 +1,10 @@
1
1
  # ashlr-stack-mcp
2
2
 
3
- > MCP server for [Ashlr Stack](https://stack.ashlr.ai). Exposes 19 tools and up to 3 resources so Claude Code / Cursor / Windsurf / Codex can provision every third-party service in a project with one call.
3
+ > MCP server for [Ashlr Stack](https://stack.ashlr.ai). Exposes 19 tools and up to 3 resources for inspecting and configuring supported services from MCP clients.
4
4
 
5
5
  ## What it does
6
6
 
7
- `stack` is a CLI. `ashlr-stack-mcp` is the same capabilities as MCP tools so your coding agent can drive Stack directly. Ask Claude "add Supabase to this project" and it calls `stack_add`, which walks OAuth, provisions the project, writes secrets through Phantom, and updates `.mcp.json` — all without leaving the chat.
7
+ `stack` is a CLI. `ashlr-stack-mcp` is the same capabilities as MCP tools so your coding agent can drive Stack directly. An agent can request `stack_add` for a supported provider; authentication, resource setup and configuration changes depend on the adapter and authorization. Inspect the result and any changes.
8
8
 
9
9
  ## Install
10
10
 
@@ -26,7 +26,7 @@ bun add -g ashlr-stack-mcp @ashlr/stack
26
26
  npm i -g ashlr-stack-mcp @ashlr/stack
27
27
  ```
28
28
 
29
- Every tool runs the `stack` CLI. The server resolves it in this order: the executable specified by `STACK_BIN`, the installed `@ashlr/stack` dependency's bin, then `stack` on PATH. If none is available, the server can still start and list tools, but calls fail with a CLI error. The npm 0.1.1 release runs on Bun, so Bun must be installed for that release.
29
+ Every tool runs the `stack` CLI. The server resolves it in this order: the executable specified by `STACK_BIN`, the installed `@ashlr/stack` dependency's bin, then `stack` on PATH. If none is available, the server can still start and list tools, but calls fail with a CLI error. The npm CLI and MCP packages in this release declare Node.js >= 20 and use Node entrypoints. Check your installed package manifests; source development uses Bun.
30
30
 
31
31
  ## Run from a local clone
32
32
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ashlr-stack-mcp",
3
- "version": "0.3.0",
3
+ "version": "0.3.1",
4
4
  "mcpName": "io.github.ashlrai/ashlr-stack",
5
5
  "description": "MCP server for Ashlr Stack. Exposes 19 tools and 3 resources so Claude Code / Cursor / Windsurf / Codex can provision every third-party service in a project with one call.",
6
6
  "license": "MIT",
@@ -51,7 +51,7 @@
51
51
  "typecheck": "bunx tsc --noEmit"
52
52
  },
53
53
  "dependencies": {
54
- "@ashlr/stack": "^0.3.0",
54
+ "@ashlr/stack": "^0.3.1",
55
55
  "@modelcontextprotocol/sdk": "^1.0.0"
56
56
  },
57
57
  "devDependencies": {