@elisym/mcp 0.24.0 → 0.25.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 +4 -2
- package/dist/index.js +431 -347
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -112,12 +112,12 @@ The bootstrap step is unchanged - the wizard collects the passphrase interactive
|
|
|
112
112
|
| `ELISYM_AGENT` | Load agent from `~/.elisym/<name>/` (or a project-local `.elisym/<name>/`) |
|
|
113
113
|
| `ELISYM_NOSTR_SECRET` | Nostr secret key (hex or nsec) for ephemeral mode |
|
|
114
114
|
| `ELISYM_AGENT_NAME` | Agent display name (default: mcp-agent) |
|
|
115
|
-
| `ELISYM_NETWORK` | Solana network for ephemeral/auto-created identities: `
|
|
115
|
+
| `ELISYM_NETWORK` | Solana network for ephemeral/auto-created identities: `mainnet` (default) or `devnet`. It cannot override a disk-loaded agent - an agent's network is fixed at creation, and a conflicting value fails startup |
|
|
116
116
|
| `ELISYM_PASSPHRASE` | Passphrase for encrypted agent configs (optional) |
|
|
117
117
|
| `ELISYM_ALLOW_WITHDRAWAL` | Set to `1` to override per-agent `security.withdrawals_enabled` flag (CI use) |
|
|
118
118
|
| `ELISYM_ALLOW_AGENT_SWITCH` | Set to `1` to override per-agent `security.agent_switch_enabled` flag |
|
|
119
119
|
|
|
120
|
-
The RPC endpoint is always the public one for each agent's network (`api.devnet.solana.com` / `api.mainnet-beta.solana.com`). The MCP server deliberately does **not** honor `SOLANA_RPC_URL`: one process can host agents on both networks, and a process-wide override could point a devnet agent's payment path at mainnet. Creating a
|
|
120
|
+
The RPC endpoint is always the public one for each agent's network (`api.devnet.solana.com` / `api.mainnet-beta.solana.com`). The MCP server deliberately does **not** honor `SOLANA_RPC_URL`: one process can host agents on both networks, and a process-wide override could point a devnet agent's payment path at mainnet. New agents are mainnet by default and move real funds. Creating a devnet agent to experiment with: `npx @elisym/mcp init <name> --network devnet` (or the `create_agent` tool's `network` parameter); the network is fixed at creation, and `switch_agent` to an agent on the other network is how a session changes network. An agent created before this default flipped keeps the network its YAML records - an upgrade never re-points an existing agent at mainnet.
|
|
121
121
|
|
|
122
122
|
## Usage Examples
|
|
123
123
|
|
|
@@ -187,6 +187,8 @@ Ask <npub> with capability "review" to review the diff in this repo
|
|
|
187
187
|
|
|
188
188
|
The file-handle and diff-specific variants only affect tool-call output tokens on the customer side. Provider-side compute and on-chain payment are unchanged.
|
|
189
189
|
|
|
190
|
+
All three pay the listed price up front. When a capability advertises delegation, use the delegated counterparts instead: `submit_delegated_job` (inline input, spilled to iroh when large) and `submit_delegated_job_from_file` (file on disk). The provider pulls from your spl-approve allowance after delivering, so a metered capability bills only what the job used.
|
|
191
|
+
|
|
190
192
|
## Security
|
|
191
193
|
|
|
192
194
|
`withdraw` and `switch_agent` are gated behind opt-in flags that must be explicitly enabled per-agent:
|