How do I install the Ferris Search Setup skill?

Run npx skillmds@latest add lispking/ferris-search-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ferris Search Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ferris Search Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ferris Search Setup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ferris Search Setup?

lispking (@lispking) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ferris Search Setup by lispking — Agent Skill

Name: Ferris Search Setup
Author: lispking

Ferris Search Setup

CRITICAL: Use for ferris-search installation and configuration. Triggers on: ferris-search install, mcp add ferris-search, setup ferris-search, DEFAULT_SEARCH_ENGINE, ALLOWED_SEARCH_ENGINES, BRAVE_API_KEY, EXA_API_KEY, FIRECRAWL_API_KEY, JINA_API_KEY, TAVILY_API_KEY, USE_PROXY, ferris-search config, ferris-search build, ferris-search Docker, 安装ferris-search, 配置搜索引擎, MCP服务器配置, 代理设置

lispking 2f9332a 2 files · 8.0 KB Updated Sep 17, 2026

File contents

ferris-search Setup & Configuration Skill

Version: ferris-search 0.1.0 | Last Updated: 2026-03-30

You are an expert at installing and configuring the ferris-search MCP server. Help users by:

Setup: Guide through build, install, and MCP registration
Configuration: Explain env vars and their effects

Documentation

Refer to the local files for detailed documentation:

./references/configuration.md - All environment variables and their effects

IMPORTANT: Documentation Completeness Check

Before answering questions, Claude MUST:

Read ./references/configuration.md
If file read fails: still answer based on SKILL.md patterns

Key Patterns

Build & register with Claude Code

cargo build --release
claude mcp add ferris-search ./target/release/ferris-search

With environment variables

claude mcp add ferris-search ./target/release/ferris-search \
  -e DEFAULT_SEARCH_ENGINE=bing \
  -e ALLOWED_SEARCH_ENGINES=bing,duckduckgo,brave

Claude Desktop / Cursor (mcp-config.json)

{
  "mcpServers": {
    "ferris-search": {
      "command": "/path/to/ferris-search",
      "env": {
        "DEFAULT_SEARCH_ENGINE": "bing",
        "ALLOWED_SEARCH_ENGINES": "bing,duckduckgo,brave,baidu",
        "EXA_API_KEY": "your-key-here"
      }
    }
  }
}

With proxy

claude mcp add ferris-search ./target/release/ferris-search \
  -e USE_PROXY=true \
  -e PROXY_URL=http://127.0.0.1:7890

Docker

docker build -t ferris-search .
docker run -e DEFAULT_SEARCH_ENGINE=bing ferris-search

Configuration Reference

Env Var	Default	Description
`DEFAULT_SEARCH_ENGINE`	`bing`	Engine used when `engines` param is omitted
`ALLOWED_SEARCH_ENGINES`	all 14 engines	Comma-separated allow-list
`BRAVE_API_KEY`	—	Required only for `brave` engine
`EXA_API_KEY`	—	Required only for `exa` engine
`FIRECRAWL_API_KEY`	—	Required only for `firecrawl` engine
`JINA_API_KEY`	—	Required only for `jina` engine
`TAVILY_API_KEY`	—	Required only for `tavily` engine
`GITHUB_TOKEN`	—	Optional for `github`/`github_code` engines (60→5000 req/hr)
`USE_PROXY`	`false`	Enable HTTP/SOCKS5 proxy
`PROXY_URL`	`http://127.0.0.1:7890`	Proxy address
`ENABLE_HTTP_SERVER`	`false`	Enable HTTP/SSE transport alongside stdio
`MODE`	`stdio`	Transport mode: `stdio`, `http`, or `both`
`RUST_LOG`	`info`	Log level: `debug`, `info`, `warn`, `error`

When Writing Code

Always build with --release for production use (~8 MB binary, <10 ms startup)
Set ALLOWED_SEARCH_ENGINES to only the engines you need — reduces attack surface
Never commit EXA_API_KEY, FIRECRAWL_API_KEY, JINA_API_KEY, TAVILY_API_KEY, BRAVE_API_KEY, or GITHUB_TOKEN to source control — use env var injection
For Chinese content workflows, include baidu, csdn, juejin, zhihu in allow-list

When Answering Questions

claude mcp add is the recommended path for Claude Code users
JSON config is needed for Claude Desktop / Cursor
Proxy support works for all engines including those behind GFW
ALLOWED_SEARCH_ENGINES acts as an allow-list — engines not listed are silently filtered out

---name: ferris-search-setupdescription: CRITICAL: Use for ferris-search installation and configuration. Triggers on: ferris-search install, mcp add ferris-search, setup ferris-search, DEFAULT_SEARCH_ENGINE, ALLOWED_SEARCH_ENGINES, BRAVE_API_KEY, EXA_API_KEY, FIRECRAWL_API_KEY, JINA_API_KEY, TAVILY_API_KEY, USE_PROXY, ferris-search config, ferris-search build, ferris-search Docker, 安装ferris-search, 配置搜索引擎, MCP服务器配置, 代理设置---# ferris-search Setup & Configuration Skill> **Version:** ferris-search 0.1.0 | **Last Updated:** 2026-03-30You are an expert at installing and configuring the `ferris-search` MCP server. Help users by:- **Setup**: Guide through build, install, and MCP registration- **Configuration**: Explain env vars and their effects## DocumentationRefer to the local files for detailed documentation:- `./references/configuration.md` - All environment variables and their effects## IMPORTANT: Documentation Completeness Check**Before answering questions, Claude MUST:**1. Read `./references/configuration.md`2. If file read fails: still answer based on SKILL.md patterns## Key Patterns### Build & register with Claude Code```bashcargo build --releaseclaude mcp add ferris-search ./target/release/ferris-search```### With environment variables```bashclaude mcp add ferris-search ./target/release/ferris-search \ -e DEFAULT_SEARCH_ENGINE=bing \ -e ALLOWED_SEARCH_ENGINES=bing,duckduckgo,brave```### Claude Desktop / Cursor (mcp-config.json)```json{ "mcpServers": { "ferris-search": { "command": "/path/to/ferris-search", "env": { "DEFAULT_SEARCH_ENGINE": "bing", "ALLOWED_SEARCH_ENGINES": "bing,duckduckgo,brave,baidu", "EXA_API_KEY": "your-key-here" } } }}```### With proxy```bashclaude mcp add ferris-search ./target/release/ferris-search \ -e USE_PROXY=true \ -e PROXY_URL=http://127.0.0.1:7890```### Docker```bashdocker build -t ferris-search .docker run -e DEFAULT_SEARCH_ENGINE=bing ferris-search```## Configuration Reference| Env Var | Default | Description ||---------|---------|-------------|| `DEFAULT_SEARCH_ENGINE` | `bing` | Engine used when `engines` param is omitted || `ALLOWED_SEARCH_ENGINES` | all 14 engines | Comma-separated allow-list || `BRAVE_API_KEY` | — | Required only for `brave` engine || `EXA_API_KEY` | — | Required only for `exa` engine || `FIRECRAWL_API_KEY` | — | Required only for `firecrawl` engine || `JINA_API_KEY` | — | Required only for `jina` engine || `TAVILY_API_KEY` | — | Required only for `tavily` engine || `GITHUB_TOKEN` | — | Optional for `github`/`github_code` engines (60→5000 req/hr) || `USE_PROXY` | `false` | Enable HTTP/SOCKS5 proxy || `PROXY_URL` | `http://127.0.0.1:7890` | Proxy address || `ENABLE_HTTP_SERVER` | `false` | Enable HTTP/SSE transport alongside stdio || `MODE` | `stdio` | Transport mode: `stdio`, `http`, or `both` || `RUST_LOG` | `info` | Log level: `debug`, `info`, `warn`, `error` |## When Writing Code1. Always build with `--release` for production use (~8 MB binary, <10 ms startup)2. Set `ALLOWED_SEARCH_ENGINES` to only the engines you need — reduces attack surface3. Never commit `EXA_API_KEY`, `FIRECRAWL_API_KEY`, `JINA_API_KEY`, `TAVILY_API_KEY`, `BRAVE_API_KEY`, or `GITHUB_TOKEN` to source control — use env var injection4. For Chinese content workflows, include `baidu`, `csdn`, `juejin`, `zhihu` in allow-list## When Answering Questions1. `claude mcp add` is the recommended path for Claude Code users2. JSON config is needed for Claude Desktop / Cursor3. Proxy support works for all engines including those behind GFW4. `ALLOWED_SEARCH_ENGINES` acts as an allow-list — engines not listed are silently filtered out

Frequently asked questions