activeadmin_mcp 0.0.3 → 0.0.4
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.
- checksums.yaml +4 -4
- data/README.md +78 -0
- data/lib/activeadmin_mcp/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 5eb6b95afa3bf6d96a2ae33ced52621014f535f11542dcbee38b88638580e6a9
|
|
4
|
+
data.tar.gz: c87121826ee5e29805cfa9f3fd8faf1f5042698ec94d46c5fbd7bbc90f08b3f3
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 6b7a903b975a980a23246e944b2e321fab7019ac218c06a51f6645a5e0d7577951cb4bdce9c4319e7184d9b5f031b96320ee874666b8d28c1814850cb59533b9
|
|
7
|
+
data.tar.gz: 3a069d2f4d7a69038f3f96153e67911472f43fabb64aa4fc7a3ccdb421684cd6cabd126d208fbe9671dc1fa7c7ecc7f2789d68638f4e84cfdcb78e45d90ddb7b
|
data/README.md
CHANGED
|
@@ -203,6 +203,84 @@ end
|
|
|
203
203
|
}
|
|
204
204
|
```
|
|
205
205
|
|
|
206
|
+
## Claude Desktop (MCPB bundle)
|
|
207
|
+
|
|
208
|
+
Claude Code talks to the server over HTTP directly, but **Claude Desktop** cannot:
|
|
209
|
+
its remote connector UI has no way to send an API token header. The `mcpb/`
|
|
210
|
+
directory solves this with an
|
|
211
|
+
[MCP bundle](https://claude.com/docs/connectors/building/mcpb) — a `.mcpb` file
|
|
212
|
+
your colleagues install with a double-click.
|
|
213
|
+
|
|
214
|
+
Inside the bundle is a small Node script that speaks stdio to Claude Desktop and
|
|
215
|
+
forwards every message, unchanged, to your server over HTTPS with the token
|
|
216
|
+
attached. It has no dependencies and adds no capabilities of its own, so the
|
|
217
|
+
tools it exposes are exactly the ones your server exposes.
|
|
218
|
+
|
|
219
|
+
```
|
|
220
|
+
Claude Desktop ──stdio──▶ mcpb proxy ──HTTPS + token──▶ your Rails app
|
|
221
|
+
```
|
|
222
|
+
|
|
223
|
+
### Building the bundle
|
|
224
|
+
|
|
225
|
+
Requires Node 18 or newer. From the repository root:
|
|
226
|
+
|
|
227
|
+
```bash
|
|
228
|
+
cd mcpb
|
|
229
|
+
npm test # no dependencies to install
|
|
230
|
+
npx @anthropic-ai/mcpb pack . ../activeadmin-mcp.mcpb
|
|
231
|
+
```
|
|
232
|
+
|
|
233
|
+
That writes `activeadmin-mcp.mcpb` (a zip of `manifest.json`, `package.json` and
|
|
234
|
+
`server/index.js`) to the repository root, ready to distribute. Bump `version`
|
|
235
|
+
in **both** `mcpb/manifest.json` and `mcpb/package.json` before packing a
|
|
236
|
+
release — Claude Desktop uses the manifest version to detect upgrades.
|
|
237
|
+
|
|
238
|
+
CI packs the bundle on every push and attaches it as a build artifact, so you
|
|
239
|
+
can also download a build from the Actions tab rather than packing it yourself.
|
|
240
|
+
|
|
241
|
+
Distribute the file however suits you: an internal file share, a GitHub release
|
|
242
|
+
asset, or an S3 bucket. Anyone with the file can install it, but it is inert
|
|
243
|
+
without a token.
|
|
244
|
+
|
|
245
|
+
### Installing
|
|
246
|
+
|
|
247
|
+
1. **Generate a token.** Sign in to your admin panel, go to **MCP Tokens**, name
|
|
248
|
+
the token after the machine you are installing on (e.g. "Claude Desktop —
|
|
249
|
+
work laptop") and copy it. It is shown only once.
|
|
250
|
+
2. **Install the bundle.** Double-click the `.mcpb` file, or drag it onto the
|
|
251
|
+
Claude Desktop window, or use **Settings → Extensions → Advanced settings →
|
|
252
|
+
Install Extension…**.
|
|
253
|
+
3. **Fill in the three settings** Claude Desktop prompts for:
|
|
254
|
+
|
|
255
|
+
| Setting | Value |
|
|
256
|
+
|---------|-------|
|
|
257
|
+
| Server URL | The full MCP endpoint, e.g. `https://admin.example.com/admin/mcp` |
|
|
258
|
+
| API token | The token from step 1 (stored in the OS keychain, never shown again) |
|
|
259
|
+
| Authentication header | `Authorization`, unless your app sets a custom [`auth_header_name`](#custom-auth-header) |
|
|
260
|
+
|
|
261
|
+
4. **Check it works.** Start a new chat and ask Claude to list the admin
|
|
262
|
+
resources it can see. You should get back the resources your account can read.
|
|
263
|
+
|
|
264
|
+
Installation is per-person: each colleague installs the bundle and generates
|
|
265
|
+
their own token, so every MCP call is attributed to them and constrained by
|
|
266
|
+
their own admin permissions.
|
|
267
|
+
|
|
268
|
+
### Revoking access
|
|
269
|
+
|
|
270
|
+
A token is a long-lived credential granting everything that user can do in
|
|
271
|
+
admin. Revoke one from the same **MCP Tokens** page — the `Last used` column
|
|
272
|
+
shows which tokens are still live. Revoking takes effect immediately; the
|
|
273
|
+
installed bundle simply starts reporting an authentication failure.
|
|
274
|
+
|
|
275
|
+
### Troubleshooting
|
|
276
|
+
|
|
277
|
+
| Symptom | Cause |
|
|
278
|
+
|---------|-------|
|
|
279
|
+
| "The server rejected the API token (HTTP 401)" | The token is wrong, revoked, or being sent in the wrong header. Check the **Authentication header** setting matches your `auth_header_name`. |
|
|
280
|
+
| "Could not reach …" | The URL is wrong or unreachable from this machine — check VPN, and that the URL includes the full mount path. |
|
|
281
|
+
| The extension shows no tools | Claude Desktop only refreshes tools on connect. Toggle the extension off and on in Settings → Extensions. |
|
|
282
|
+
| Anything else | Claude Desktop's extension logs carry the proxy's stderr output, each line prefixed `[activeadmin_mcp]`. |
|
|
283
|
+
|
|
206
284
|
## Configuration
|
|
207
285
|
|
|
208
286
|
The generator writes an initializer to
|