@lerianstudio/matcher-mcp 1.0.0-beta.5 → 1.0.0
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 +9 -5
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -64,11 +64,15 @@ as a *remote / HTTP* server.
|
|
|
64
64
|
|
|
65
65
|
### 1. Get an endpoint
|
|
66
66
|
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
- **Connect to a deployed server (recommended).** Point your client at
|
|
70
|
-
`matcher-mcp` (the GHCR image), e.g. `https://matcher-mcp.example.com/mcp`.
|
|
71
|
-
|
|
67
|
+
Three options for `<mcp-url>`:
|
|
68
|
+
|
|
69
|
+
- **Connect to a deployed server (recommended for clients).** Point your client at
|
|
70
|
+
a running `matcher-mcp` (the GHCR image), e.g. `https://matcher-mcp.example.com/mcp`.
|
|
71
|
+
Clients connect remotely and install nothing locally.
|
|
72
|
+
- **Local matcher dev (repo clone).** `make up` brings the relay up as a compose
|
|
73
|
+
service on `:4019` alongside the rest of the stack (`restart: unless-stopped`,
|
|
74
|
+
so it stays up — no separate process to babysit). Use `http://localhost:4019/mcp`.
|
|
75
|
+
- **Run it standalone with `npx`.** `@lerianstudio/matcher-mcp` is a **public**
|
|
72
76
|
package (Apache-2.0) — no registry auth needed. Start the relay (binds `:4019`)
|
|
73
77
|
pointed at your Matcher API:
|
|
74
78
|
|