Scouts-AI-MCP
Model Context Protocol server exposing the SCOUTS-AI web search API as a single web_search tool for AI agents. No API key required.
README
scouts-ai-mcp
Model Context Protocol (MCP) server that exposes the SCOUTS-AI web search API as a single web_search tool for AI agents, LLM apps, answer engines and GEO workflows.
- One tool, no API key. Backed by
GET https://scouts-ai.com/api/search. - Drop-in for Claude Desktop, Cursor, Open WebUI, Continue, Cline and any MCP host.
- Python ≥ 3.10,
fastmcpv2,httpx. - MIT licensed.
Install
pip install scouts-ai-mcp
Run (stdio)
scouts-ai-mcp
That's it. Wire it into your MCP host of choice — for example, Claude Desktop's claude_desktop_config.json:
{
"mcpServers": {
"scouts-ai": {
"command": "scouts-ai-mcp"
}
}
}
Run (HTTP)
For remote MCP hosts and self-hosted bridges:
scouts-ai-mcp --transport http --host 127.0.0.1 --port 8765
Run (Docker)
A multi-arch (linux/amd64 + linux/arm64) image is published to Docker
Hub as kecven/scouts-ai-mcp.
It runs the MCP server in streamable HTTP mode on port 8765 and exposes
the web_search tool at http://localhost:8765/mcp. No API key, no
external dependencies.
Quick start:
docker run --rm -p 8765:8765 kecven/scouts-ai-mcp:0.1.5
Then point any streamable-HTTP MCP host at http://localhost:8765/mcp
(or, when run behind a public proxy, https://<your-host>/mcp).
Override the upstream API base URL:
docker run --rm -p 8765:8765 \
-e SCOUTS_AI_BASE_URL=https://scouts-ai.com \
kecven/scouts-ai-mcp:0.1.5
Append CLI args (the image entrypoint is scouts-ai-mcp):
docker run --rm -p 8765:8765 kecven/scouts-ai-mcp:0.1.5 --log-level=DEBUG
Available tags:
kecven/scouts-ai-mcp:0.1.5— pinned, recommended for production.kecven/scouts-ai-mcp:0.1— minor-version rolling tag.kecven/scouts-ai-mcp:latest— latest stable release.
Build and push locally (requires docker buildx):
docker buildx build \
--platform linux/amd64,linux/arm64 \
-f Dockerfile.hosted \
-t kecven/scouts-ai-mcp:0.1.5 \
-t kecven/scouts-ai-mcp:0.1 \
-t kecven/scouts-ai-mcp:latest \
--push .
The image runs as a non-root user (scouts, uid 1001) and includes a
TCP-level HEALTHCHECK on 127.0.0.1:8765 (the streamable HTTP
endpoint does not return 200 on plain GET, so an HTTP probe would be
unreliable).
Tool: web_search
| Parameter | Type | Default | Description |
|---|---|---|---|
query |
string | — | Search query, 1–512 chars. |
lang |
string | en |
BCP-47 language code (e.g. en, en-US). |
page |
int | 1 |
1-based page number, 1–10. |
Returns a compact JSON object mirroring the SCOUTS-AI response shape:
{
"query": "rust async runtime",
"lang": "en",
"page": 1,
"pageSize": 10,
"cached": false,
"tookMs": 412,
"results": [
{
"title": "Tokio - An asynchronous runtime for Rust",
"url": "https://tokio.rs/",
"content": "Tokio is an asynchronous runtime for the Rust programming language...",
"publishedAt": "2025-11-14T00:00:00Z",
"engine": "duckduckgo"
}
]
}
Error handling
The tool raises ToolError (rendered as an MCP tool error) when:
- The query is empty/too long or
lang/pageare invalid → invalid arguments. - The upstream returns
429→ rate limit exceeded; honorsRetry-Afterwhen present. - The upstream returns
5xxor the network call fails → SCOUTS-AI temporarily unavailable. - The upstream returns a structured
4xxerror envelope → forwards the code and message.
Configuration
All settings are environment variables. Defaults match the public SCOUTS-AI deployment.
| Variable | Default | Description |
|---|---|---|
SCOUTS_AI_BASE_URL |
https://scouts-ai.com |
Base URL of the SCOUTS-AI API. |
SCOUTS_AI_TIMEOUT_S |
5.0 |
HTTP timeout in seconds (0.1–60). |
SCOUTS_AI_USER_AGENT |
scouts-ai-mcp/0.1.5 |
User-Agent header. |
SCOUTS_AI_DEFAULT_LANG |
en |
Default lang when the tool omits it. |
SCOUTS_AI_MAX_QUERY_LENGTH |
512 |
Reject queries longer than this. |
SCOUTS_AI_MAX_PAGE |
10 |
Reject page numbers above this. |
Development
git clone https://github.com/kecven/scouts-ai-mcp.git
cd scouts-ai-mcp
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
pytest
License
MIT — see LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.