timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
MCP server for iFlow Search web search, image search, and URL fetch tools.
Skills that teach the AI this kind of work; they work alongside this one
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 3/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 3/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install iFlow Search. Follow https://mcp.popnx.com/i/zhengyanglsun-iflow-search.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a iFlow Search key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server iFlow Search for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "iflow-search": { "command": "npx", "args": [ "-y", "@iflow-ai/search-mcp" ], "env": { "IFLOW_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For IFLOW_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the iFlow Search tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
SettingsDeveloperEdit Config
{
"mcpServers": {
"iflow-search": {
"command": "npx",
"args": [
"-y",
"@iflow-ai/search-mcp"
],
"env": {
"IFLOW_API_KEY": "your-value"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use iFlow Search and tell me what you can do for me, then show me one thing✓ If Claude says it is using iFlow Search or shows a iFlow Search tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
IFLOW_MCP_CLIENT Optional MCP client slug forwarded to iFlow as the IFlow-MCP-Client header. Matches /^[a-z0-9._-]{1,64}$/.IFLOW_MCP_CLIENT_VERSION Optional MCP client version forwarded to iFlow as the IFlow-MCP-Client-Version header. Only honored when IFLOW_MCP_CLIENT is also set.IFLOW_BASE_URL Optional override for the iFlow Search API base URL. Defaults to https://platform.iflow.cn.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect iFlow Search yet
iFlow Search runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect iFlow Search
Works with Claude Code, with some setup first
You need a iFlow Search key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server iFlow Search for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user iflow-search --env IFLOW_API_KEY=your-value -- npx -y @iflow-ai/search-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For IFLOW_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the iFlow Search tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user iflow-search --env IFLOW_API_KEY=your-value -- npx -y @iflow-ai/search-mcpReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see iFlow Search listed as connected
Use iFlow Search and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using iFlow Search or shows a iFlow Search tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
IFLOW_MCP_CLIENT Optional MCP client slug forwarded to iFlow as the IFlow-MCP-Client header. Matches /^[a-z0-9._-]{1,64}$/.IFLOW_MCP_CLIENT_VERSION Optional MCP client version forwarded to iFlow as the IFlow-MCP-Client-Version header. Only honored when IFLOW_MCP_CLIENT is also set.IFLOW_BASE_URL Optional override for the iFlow Search API base URL. Defaults to https://platform.iflow.cn.Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a iFlow Search key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server iFlow Search for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "iflow-search": { "command": "npx", "args": [ "-y", "@iflow-ai/search-mcp" ], "env": { "IFLOW_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For IFLOW_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the iFlow Search tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
In the iFlow Search settings, IFLOW_API_KEY is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use iFlow Search and tell me what you can do for me, then show me one thing✓ If Cursor says it is using iFlow Search or shows a iFlow Search tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
IFLOW_MCP_CLIENT Optional MCP client slug forwarded to iFlow as the IFlow-MCP-Client header. Matches /^[a-z0-9._-]{1,64}$/.IFLOW_MCP_CLIENT_VERSION Optional MCP client version forwarded to iFlow as the IFlow-MCP-Client-Version header. Only honored when IFLOW_MCP_CLIENT is also set.IFLOW_BASE_URL Optional override for the iFlow Search API base URL. Defaults to https://platform.iflow.cn.Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a iFlow Search key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server iFlow Search for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "iflow-search": { "type": "stdio", "command": "npx", "args": [ "-y", "@iflow-ai/search-mcp" ], "env": { "IFLOW_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For IFLOW_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the iFlow Search tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
In the iFlow Search settings, IFLOW_API_KEY is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use iFlow Search and tell me what you can do for me, then show me one thing✓ If VS Code says it is using iFlow Search or shows a iFlow Search tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
IFLOW_MCP_CLIENT Optional MCP client slug forwarded to iFlow as the IFlow-MCP-Client header. Matches /^[a-z0-9._-]{1,64}$/.IFLOW_MCP_CLIENT_VERSION Optional MCP client version forwarded to iFlow as the IFlow-MCP-Client-Version header. Only honored when IFLOW_MCP_CLIENT is also set.IFLOW_BASE_URL Optional override for the iFlow Search API base URL. Defaults to https://platform.iflow.cn.Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user iflow-search --env IFLOW_API_KEY=your-value -- npx -y @iflow-ai/search-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"iflow-search": {
"command": "npx",
"args": [
"-y",
"@iflow-ai/search-mcp"
],
"env": {
"IFLOW_API_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"iflow-search": {
"command": "npx",
"args": [
"-y",
"@iflow-ai/search-mcp"
],
"env": {
"IFLOW_API_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"iflow-search": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@iflow-ai/search-mcp"
],
"env": {
"IFLOW_API_KEY": "your-value"
}
}
}
}IFLOW_API_KEY secret required envIFLOW_MCP_CLIENT envIFLOW_MCP_CLIENT_VERSION envIFLOW_BASE_URL envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: @iflow-ai/search-mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account zhengyanglsun, which owns the repo
Code last changed 6 months ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for @iflow-ai/search-mcp@0.1.0
Checks only this package version, not every dependency · checked Nov 16, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/zhengyanglsun-iflow-search)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: IFLOW_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 6 months ago, and the latest version (0.1.0) reached the registry 6 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
Search and read Empryo's documentation. Read-only, no auth, no local access.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| This one iFlow Search | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | Yes | Yes | Yes | No | No |
| Basic checks | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MCP (Model Context Protocol) server for iFlow Search — exposes web search, image search, and web fetch to any MCP client (Claude Code, Claude Desktop, and other compatible hosts).
Built on @iflow-ai/search-core. Same three tools as @iflow-ai/search-langchain, same names, same shapes — so prompts that drive an iFlow-search-tool agent under LangChain keep working verbatim under MCP.
0.1.0)@iflow-ai/search-mcp@0.1.0 is live on dist-tag latest. Bare npm install @iflow-ai/search-mcp resolves the stable release. @next remains the prerelease channel and currently points at 0.1.0-pre.2; use it only when you need to track an upcoming pre-cut. Run npm view @iflow-ai/search-mcp dist-tags --json to read live state.
The Official MCP Registry entry io.github.zhengyanglsun/iflow-search publishes 0.1.0 as the current isLatest version (0.1.0-pre.2 remains visible only as a historical entry — see Official MCP Registry below). The registry is metadata-only; the package itself installs from npm.
iflow_web_search, iflow_image_search, iflow_web_fetch.env block (never via CLI flags, dotfiles, keychain, or file discovery).pnpm add @iflow-ai/search-mcp
npm install @iflow-ai/search-mcp
Node ≥ 18.
This server is listed in the Official MCP Registry:
io.github.zhengyanglsun/iflow-search@iflow-ai/search-mcp on dist-tag latest (0.1.0)0.1.0 (isLatest: true, status: active). 0.1.0-pre.2 remains as a historical entry only.stdioThe registry stores metadata only — the package itself still installs from npm. MCP clients launch the server with npx -y @iflow-ai/search-mcp, which resolves the current stable release (0.1.0), or pin a concrete version (e.g. @iflow-ai/search-mcp@0.1.0) for reproducibility. @next is still available for pre-cut testing.
mcpServers JSONAdd an entry to your client's mcpServers configuration:
{
"mcpServers": { "iflow-search": { "command": "npx", "args": ["-y", "@iflow-ai/search-mcp"], "env": { "IFLOW_API_KEY": "YOUR_IFLOW_API_KEY", "IFLOW_MCP_CLIENT": "claude-code" } } } }
For Claude Desktop, the wiring is identical but set IFLOW_MCP_CLIENT to claude-desktop so backend analytics can tell the two apart:
"env": {
"IFLOW_API_KEY": "YOUR_IFLOW_API_KEY", "IFLOW_MCP_CLIENT": "claude-desktop" }
IFLOW_MCP_CLIENT is optional — see the Configuration table for the allowed value set. If absent, no IFlow-MCP-Client header is sent (the request is still attributed to IFlow-Source: mcp).
Do not commit a real key. Put
YOUR_IFLOW_API_KEYin version control
and inject the real value at runtime (your client's secret store, a local
override file ignored by git, a
direnvblock, etc.).@iflow-ai/search-mcp
never reads from disk and will not pick up a
.envautomatically.
Verified host. Claude Code is a verified MCP host for this package —
end-to-end stdio smoke green on
@iflow-ai/search-mcp@0.1.0-pre.2with
Claude Code CLI
2.1.148-20260509.2, all three tools exercised against the
real iFlow Search API. For one-off smoke / evaluation runs that must not
touch your persistent Claude Code config, use a session-scoped config file
with
claude -p --strict-mcp-config --mcp-config --no-session-persistence …
and let
IFLOW_API_KEYreach the MCP child via Claude Code's parent-env
spread (do NOT write the key into the temp
mcp.json). The reproduction
sketch is in
Add the server to ~/.hermes/config.yaml:
# ~/.hermes/config.yaml
mcp_servers: iflow-search: command: npx args:
Verify Hermes can spawn the server and list its three tools:
hermes mcp test iflow-search
Notes:
IFLOW_API_KEY must be set inside the server's env: block. Hermes only forwards a small allowlist of parent-shell variables to MCP subprocesses (PATH, HOME, USER, …); anything else, including your iFlow key, has to be declared here. Keep YOUR_IFLOW_API_KEY as a placeholder in anything you share — never commit the real key.IFLOW_MCP_CLIENT: hermes tags every outbound request with the IFlow-MCP-Client: hermes header so backend analytics can distinguish Hermes traffic from Claude Code / Claude Desktop. The field is optional but recommended.0.1.0 is on dist-tag latest; the bare @iflow-ai/search-mcp shown above resolves it. Pin to the concrete version your registry index advertises (e.g. @iflow-ai/search-mcp@0.1.0) when you want deterministic upgrades — run npm view @iflow-ai/search-mcp dist-tags --json to read the current state. @next (0.1.0-pre.2 at time of writing) is still published for pre-cut testing.url / headers fields are needed.OpenCode is a terminal coding agent with first-class stdio MCP support. Configuration goes in opencode.json (project-scoped) or ~/.config/opencode/opencode.json (user-scoped).
Two things make OpenCode's wiring different from the Claude / Hermes blocks above:
environment, not env. command and args are folded into a single command: [...] array.packages/opencode/src/mcp/index.ts in anomalyco/opencode: env: { ...process.env, ...mcp.environment }). Exporting IFLOW_API_KEY in the shell that launches OpenCode is sufficient — the key never appears in any committed file. The environment map does not expand ${VAR} shell syntax (Effect schema Record , taken verbatim), so writing "${IFLOW_API_KEY}" as a value would send the literal string to the MCP child and break iFlow auth.Export the key once in your shell:
export IFLOW_API_KEY="YOUR_IFLOW_API_KEY"
Then put only non-secret values in opencode.json:
{
"mcp": { "iflow-search": { "type": "local", "command": ["npx", "-y", "@iflow-ai/search-mcp@next"], "environment": { "IFLOW_MCP_CLIENT": "opencode" }, "enabled": true } } }
IFLOW_MCP_CLIENT: opencode is accepted by the existing [a-z0-9._-]{1,64} validation in packages/search-mcp/src/config.ts — no code change is needed to add OpenCode as a host slug.
Verify the wiring without launching the TUI:
opencode mcp list
A successful run prints ✓ iflow-search connected. Add --print-logs --log-level INFO to confirm tool discovery — OpenCode logs service=mcp key=iflow-search toolCount=3 create() successfully created client once the child returns tools/list.
**OpenCode prefixes MCP tools with the server name in its tool
registry.** Your LLM will see
iflow-search_iflow_web_search,
iflow-search_iflow_image_search,iflow-search_iflow_web_fetch. The
raw MCP names returned by
tools/listremainiflow_web_search/
iflow_image_search/iflow_web_fetch; theiflow-search_prefix
is OpenCode's namespace, not part of this package.
stdio is the supported transport here. OpenCode also supports remote MCP (type: "remote" with url), but this package only ships a stdio binary — no SSE / streamable-HTTP recommendation applies.
CrewAI is a Python multi-agent framework. It consumes MCP servers through the MCPServerAdapter class shipped in crewai-tools[mcp], which spawns the stdio child and exposes each MCP tool as a CrewAIMCPTool your Agents can call.
This path uses the existing published `@iflow-ai/search-mcp` stdio MCP server:
crewai-tools[mcp] already bridges any MCP stdio server, including this one.IFLOW_API_KEY in the parent shell env, not hard-coded in Python source. StdioServerParameters.env accepts a dict that is passed to the MCP child as its process.env; spreading os.environ into it is sufficient to forward the key without ever writing it to a tracked file.Install (crewai-tools requires Python 3.10–3.13):
pip install "crewai-tools[mcp]"
Minimal usage:
import os
from crewai_tools import MCPServerAdapter from mcp import StdioServerParameters
server_params = StdioServerParameters( command="npx", args=["-y", "@iflow-ai/search-mcp@next"], env={**os.environ, "IFLOW_MCP_CLIENT": "crewai"}, )
with MCPServerAdapter(server_params) as tools: print([tool.name for tool in tools])
CrewAI does not prefix MCP tool names with the server slug — the three names listed by MCPServerAdapter are the raw MCP names emitted by this package: iflow_web_search, iflow_image_search, iflow_web_fetch. A model-driven Crew sees them under those same names.
IFLOW_MCP_CLIENT="crewai" is accepted by the existing [a-z0-9._-]{1,64} validation in packages/search-mcp/src/config.ts — no code change is required to add CrewAI as a host slug.
Tested scope. The recorded CrewAI smoke verified
MCPServerAdaptertool discovery (tools/listreturned all three
expected tools) and direct
CrewAIMCPTool.run(**kwargs)calls
against the real iFlow API. The full CrewAI
Agent/Task/
CrewLLM-driven tool-selection loop was not exercised — it
requires an authenticated LLM provider, which is outside this
package's wire path. See
for the smoke detail.
Cline is a VS Code coding agent with built-in stdio MCP support. It reads MCP server definitions from ~/.cline/mcp.json (macOS/Linux; equivalent per-user path on Windows).
Add an iflow-search entry pointing at the stable package — npx -y resolves the current latest release without a global install:
{
"mcpServers": { "iflow-search": { "command": "npx", "args": ["-y", "@iflow-ai/search-mcp"], "env": { "IFLOW_API_KEY": "YOUR_IFLOW_API_KEY", "IFLOW_MCP_CLIENT": "cline" }, "autoApprove": [] } } }
After Cline reloads its MCP config, the three tools — iflow_web_search, iflow_image_search, iflow_web_fetch — show up in the agent's tool list. The same server is discoverable in the Official MCP Registry as io.github.zhengyanglsun/iflow-search; Cline still installs the package directly from npm.
IFLOW_MCP_CLIENT: cline is accepted by the existing [a-z0-9._-]{1,64} validation in packages/search-mcp/src/config.ts — no code change is required to add Cline as a host