mcp-searxng 0.2.0 → 0.2.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 +5 -47
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -41,16 +41,16 @@ npx -y @smithery/cli install @ihor-sokoliuk/server-searxng --client claude
|
|
|
41
41
|
### Installing via npm
|
|
42
42
|
|
|
43
43
|
```bash
|
|
44
|
-
npm install -g
|
|
44
|
+
npm install -g mcp-searxng
|
|
45
45
|
```
|
|
46
46
|
|
|
47
|
-
And then in your
|
|
47
|
+
And then in your MCP config file:
|
|
48
48
|
|
|
49
49
|
```json
|
|
50
50
|
{
|
|
51
51
|
"mcpServers": {
|
|
52
52
|
"searxng": {
|
|
53
|
-
"command": "mcp-
|
|
53
|
+
"command": "mcp-searxng",
|
|
54
54
|
"env": {
|
|
55
55
|
"SEARXNG_URL": "YOUR_SEARXNG_INSTANCE_URL"
|
|
56
56
|
}
|
|
@@ -68,7 +68,7 @@ And then in your `claude_desktop_config.json`:
|
|
|
68
68
|
"command": "npx",
|
|
69
69
|
"args": [
|
|
70
70
|
"-y",
|
|
71
|
-
"
|
|
71
|
+
"mcp-searxng"
|
|
72
72
|
],
|
|
73
73
|
"env": {
|
|
74
74
|
"SEARXNG_URL": "YOUR_SEARXNG_INSTANCE_URL"
|
|
@@ -83,7 +83,7 @@ And then in your `claude_desktop_config.json`:
|
|
|
83
83
|
#### Build
|
|
84
84
|
|
|
85
85
|
```bash
|
|
86
|
-
docker build -t mcp-
|
|
86
|
+
docker build -t mcp-searxng:latest -f Dockerfile .
|
|
87
87
|
```
|
|
88
88
|
|
|
89
89
|
#### Use
|
|
@@ -111,48 +111,6 @@ Add this to your `claude_desktop_config.json`:
|
|
|
111
111
|
}
|
|
112
112
|
```
|
|
113
113
|
|
|
114
|
-
## Publishing to npm
|
|
115
|
-
|
|
116
|
-
To make your library publicly available on npm:
|
|
117
|
-
|
|
118
|
-
### 1. Create an npm Account
|
|
119
|
-
|
|
120
|
-
If you don't have an npm account, create one at [npmjs.com](https://www.npmjs.com/signup).
|
|
121
|
-
|
|
122
|
-
### 2. Log in to npm
|
|
123
|
-
|
|
124
|
-
```bash
|
|
125
|
-
npm login
|
|
126
|
-
```
|
|
127
|
-
|
|
128
|
-
### 3. Prepare your package
|
|
129
|
-
|
|
130
|
-
Make sure your package.json is correctly set up with:
|
|
131
|
-
- A unique name (`@ihor-sokoliuk/server-searxng`)
|
|
132
|
-
- Version number
|
|
133
|
-
- Description
|
|
134
|
-
- Entry point
|
|
135
|
-
- Dependencies
|
|
136
|
-
|
|
137
|
-
### 4. Build your package
|
|
138
|
-
|
|
139
|
-
```bash
|
|
140
|
-
npm run build
|
|
141
|
-
```
|
|
142
|
-
|
|
143
|
-
### 5. Publish to npm
|
|
144
|
-
|
|
145
|
-
```bash
|
|
146
|
-
npm publish --access=public
|
|
147
|
-
```
|
|
148
|
-
|
|
149
|
-
For subsequent updates:
|
|
150
|
-
1. Update the version in package.json: `npm version patch|minor|major`
|
|
151
|
-
2. Run `npm publish`
|
|
152
|
-
|
|
153
|
-
### 6. Verify your package
|
|
154
|
-
|
|
155
|
-
Check that your package is available at `https://www.npmjs.com/package/@ihor-sokoliuk/server-searxng`
|
|
156
114
|
|
|
157
115
|
## License
|
|
158
116
|
|