alora-mcp 0.7.0 → 0.7.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.
- package/README.md +8 -5
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -26,13 +26,15 @@ Or in any MCP client's JSON config:
|
|
|
26
26
|
}
|
|
27
27
|
```
|
|
28
28
|
|
|
29
|
-
## Connect (
|
|
29
|
+
## Connect (one email, one click)
|
|
30
30
|
|
|
31
|
-
|
|
32
|
-
2. Run `npx alora-cli connect` in your terminal — it prints a code.
|
|
33
|
-
3. Paste the code at [alora.build/activate](https://alora.build/activate).
|
|
31
|
+
Just ask your agent to set you up. It asks for your email and calls the `account_create_and_connect` tool — you get **a single email, and one click** creates your account ($0.50 of free credit included, no card), verifies it, and authorizes the agent. No password to invent; you log into the panel later with a magic link.
|
|
34
32
|
|
|
35
|
-
The
|
|
33
|
+
Already have an account? The same flow sends you an authorize link instead — one click never creates or touches an existing account without you signing in.
|
|
34
|
+
|
|
35
|
+
Prefer the classic way? Create an account at [alora.build/register](https://alora.build/register), run `npx alora-cli connect`, and paste the code at [alora.build/activate](https://alora.build/activate).
|
|
36
|
+
|
|
37
|
+
Either way the token lands in `~/.alora/config.json`, and from then on your agent takes it from here. Full playbook for agents: [alora.build/llms.txt](https://alora.build/llms.txt).
|
|
36
38
|
|
|
37
39
|
## What your agent can do (45 tools)
|
|
38
40
|
|
|
@@ -45,6 +47,7 @@ The token lands in `~/.alora/config.json`, and from then on your agent takes it
|
|
|
45
47
|
| **Configure** | `secrets_set` (encrypted, injected as env) · `domain_connect` · `egress_ip_allocate` (static egress IP) |
|
|
46
48
|
| **Use AI inside the app** | `ai_enable` — the deployed app runs `claude -p` with the owner's own Claude account |
|
|
47
49
|
| **Buy domains** | `domain_search` · `domain_buy` — always gated on the owner's approval by email |
|
|
50
|
+
| **Be an MCP server** | your deployed app can expose its own `/mcp` endpoint, with per-customer tokens (`token_create`) and identity headers — an [MCP-first SaaS in one deploy](https://alora.build/blog/host-mcp-server) |
|
|
48
51
|
| **Know what's happening** | `analytics_summary` · `analytics_users` · `wallet_balance` · `changelog` |
|
|
49
52
|
|
|
50
53
|
## How it behaves
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "alora-mcp",
|
|
3
|
-
"version": "0.7.
|
|
4
|
-
"description": "MCP server for Alora, the cloud where your agent works
|
|
3
|
+
"version": "0.7.1",
|
|
4
|
+
"description": "MCP server for Alora, the cloud where your agent works \u2014 deploy, preview, share and run the apps your agent writes. Claude Code, Codex, Cursor and any MCP client.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
7
7
|
"alora-mcp": "src/index.js"
|