@wireweave/mcp-server 1.8.2-beta.12 → 1.8.2-beta.13
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 +14 -2
- package/dist/index.js +359 -900
- package/package.json +16 -18
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
An MCP transport adapter for Wireweave tools.
|
|
4
4
|
|
|
5
|
-
The [public tool contract](
|
|
5
|
+
The [public tool contract](https://github.com/wireweave/wireweave/blob/develop/docs/spec/TOOLING.md#5-mcp-and-agent-plugins) defines this package's APIs, behavior, configuration and compatibility. The [language contract](https://github.com/wireweave/wireweave/blob/develop/docs/spec/LANGUAGE.md) defines the DSL. Package metadata owns versions, exports, dependencies and scripts.
|
|
6
6
|
|
|
7
7
|
## Installation
|
|
8
8
|
|
|
@@ -14,9 +14,21 @@ npm install --global '@wireweave/mcp-server@<pinned-version>'
|
|
|
14
14
|
|
|
15
15
|
The installed executable is `wireweave-mcp`. Setup, transports and credentials are defined by the tool contract.
|
|
16
16
|
|
|
17
|
+
Run `wireweave-mcp` for stdio. Local parsing, validation, rendering, analysis, diffing, component discovery and JSON/Figma export need no account or API key. stdout contains only MCP protocol messages; diagnostics use stderr.
|
|
18
|
+
|
|
19
|
+
## HTTP and credentials
|
|
20
|
+
|
|
21
|
+
HTTP mode (`wireweave-mcp --http`) requires a host-provided `WIREWEAVE_MCP_TOKEN`. Clients send it as `Authorization: Bearer <token>` on every MCP operation. Use a randomly generated secret and keep it in the host's secret store. The server binds to loopback by default. `WIREWEAVE_MCP_ALLOWED_ORIGINS` is an exact, comma-separated Origin allowlist; an empty list rejects requests carrying an Origin header. An allowed browser's CORS preflight needs no bearer token and cannot create a session or execute a tool; its actual request still requires authentication. See the public tool contract for configuration bounds and session behavior.
|
|
22
|
+
|
|
23
|
+
The HTTP transport token is separate from `WIREWEAVE_API_KEY`. The latter authenticates explicitly invoked remote tools at `WIREWEAVE_API_URL` (default `https://api.wireweave.org`), using the `x-api-key` header. Remote tools include cloud storage/sharing, account/billing, gallery and hosted language guides/examples. Saving or updating a cloud wireframe sends its source and supplied metadata to that service. Local failures never fall back to remote execution. Remote calls time out after 30 seconds and do not follow redirects.
|
|
24
|
+
|
|
25
|
+
## Privacy and security
|
|
26
|
+
|
|
27
|
+
Read the [Privacy Policy](https://www.wireweave.org/privacy) for hosted-service data handling, retention and deletion requests. Local deterministic calls do not upload source or credentials. Every tool declares its read-only, destructive, idempotent and external-interaction hints; these describe behavior and do not replace authentication or authorization.
|
|
28
|
+
|
|
17
29
|
## Development
|
|
18
30
|
|
|
19
|
-
Run from the monorepo root after the [workspace setup](
|
|
31
|
+
Run from the monorepo root after the [workspace setup](https://github.com/wireweave/wireweave#workspace-commands).
|
|
20
32
|
|
|
21
33
|
```bash
|
|
22
34
|
pnpm --filter @wireweave/mcp-server run build
|