@ainecto/mcp 0.1.2 → 0.1.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.
package/README.md CHANGED
@@ -43,6 +43,8 @@ Endpoint resolution priority:
43
43
  3. `--env dev`
44
44
  4. production default, `https://ainecto.com/mcp`
45
45
 
46
+ Endpoint URLs must use `https:`. Plain `http:` is accepted only for localhost loopback targets such as `127.0.0.1`. When `AINECTO_TOKEN` is set, the CLI only sends it to the default prod/dev endpoints unless `AINECTO_ALLOW_CUSTOM_ENDPOINT_TOKEN=1` is set for an explicitly trusted custom endpoint.
47
+
46
48
  ## Connector Mode
47
49
 
48
50
  ```bash
@@ -80,7 +82,7 @@ For a non-production endpoint, pass CLI flags through the package args:
80
82
  }
81
83
  ```
82
84
 
83
- The planned official Registry server name is `io.github.codelives/ainecto`, backed by the public npm package `@ainecto/mcp`. Registry publication requires the npm package version to include a matching `mcpName` field in `package.json`; do not run `mcp-publisher publish` until the npm artifact contains that field.
85
+ The planned official Registry server name is `io.github.codelives/ainecto`, backed by the public npm package `@ainecto/mcp`. Registry publication requires the npm package version referenced by `server.json` to include a matching `mcpName` field in `package.json`.
84
86
 
85
87
  ## Catalog Sync
86
88
 
@@ -92,9 +94,9 @@ AINECTO_CATALOG_SYNC_TOKEN=... npm run sync:tools -- --env prod --check
92
94
  AINECTO_CATALOG_SYNC_TOKEN=... npm run sync:tools -- --env dev --check
93
95
  ```
94
96
 
95
- The checked-in generated catalogs are deterministic output from `tools/list`. The dev catalog has been live-synced from `https://dev.ainecto.com/mcp`; the prod catalog remains a seed fixture until prod auth is available. Presentation metadata lives separately in `src/core/catalog/enrichments.ts`.
97
+ The checked-in generated catalogs are deterministic output from `tools/list`. The prod and dev catalogs are live-synced snapshots from `https://ainecto.com/mcp` and `https://dev.ainecto.com/mcp`. Presentation metadata lives separately in `src/core/catalog/enrichments.ts`.
96
98
 
97
- `ainecto tools catalog` prints the local generated catalog. Prod output is fixture-only until authenticated prod live sync updates `generated.prod.ts` and `tools-list.prod.json`.
99
+ `ainecto tools catalog` prints the local generated catalog. Rerun authenticated `sync:tools` when prod or dev `tools/list` changes.
98
100
 
99
101
  ## Generated Friendly Commands
100
102
 
@@ -126,8 +128,8 @@ The generated `request_upload_token` and `upload_attachments` paths remain raw M
126
128
 
127
129
  ```bash
128
130
  npm pack
129
- npx -y ./ainecto-mcp-0.1.0.tgz --help
130
- npm exec --package ./ainecto-mcp-0.1.0.tgz -- ainecto --help
131
+ npx -y ./ainecto-mcp-0.1.4.tgz --help
132
+ npm exec --package ./ainecto-mcp-0.1.4.tgz -- ainecto --help
131
133
  ```
132
134
 
133
135
  ## Live Dev MCP Smoke
@@ -155,4 +157,4 @@ The smoke creates a temporary user/workspace/project/document and removes the fi
155
157
 
156
158
  - The MCP connector currently implements newline-delimited stdio JSON-RPC to HTTP JSON-RPC. Streamable HTTP SSE responses and `MCP-Session-Id` session handling are not implemented in Phase 1.
157
159
 
158
- Official MCP Registry publish is blocked until a public npm artifact includes the matching `mcpName`, the GitHub namespace owner authenticates with `mcp-publisher`, and the server metadata is submitted.
160
+ Official MCP Registry publish is pending GitHub namespace owner authentication with `mcp-publisher` and metadata submission.