morph-websearch-mcp
Web search, page fetching, and AI-powered research for MCP-compatible clients.
morph-websearch-mcp searches DuckDuckGo, fetches pages with crawl4ai, and compacts noisy webpage content with Morph. By default, results are AI-enriched into a synthesized answer with cited sources. Set enrich=false to get raw page content instead.
Features
| Tool | Description |
|---|---|
websearch |
Searches DuckDuckGo, fetches result pages, and returns AI-enriched answers with sources by default. Pass enrich=false for raw results. |
webfetch |
Fetches one URL and returns compacted markdown. |
Works without a Morph API key — falls back to uncompacted scraping with a warning. Set the key to enable AI compaction and enrichment.
Requirements
- Python 3.13 or newer
- (Optional) A Morph API key from morphllm.com/dashboard/api-keys for compaction and AI enrichment
- An MCP-compatible client, such as OpenCode, Claude Desktop, Cursor, or another client that can launch local MCP servers
Install
For most MCP clients, install the server as a standalone command:
pipx install morph-websearch-mcp
If you prefer installing into the current Python environment:
pip install morph-websearch-mcp
For local development from an existing checkout:
cd morph-websearch-mcp
uv sync
Configure Your API Key
Set MORPH_API_KEY in the environment used by your MCP client:
export MORPH_API_KEY="sk-..."
If your client is launched from a desktop app, make sure the desktop app can see that environment variable. When in doubt, put the key directly in the client MCP config instead of relying on your shell startup files.
OpenCode Setup
Add the server to your OpenCode config:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"websearch": {
"type": "local",
"command": ["websearch-mcp"],
"environment": {
"MORPH_API_KEY": "{env:MORPH_API_KEY}"
},
"enabled": true
}
}
}
Verify OpenCode can see the server:
opencode mcp list
You should see websearch listed as connected.
Generic MCP Client Setup
For clients that use the common mcpServers shape:
{
"mcpServers": {
"websearch": {
"command": "websearch-mcp",
"env": {
"MORPH_API_KEY": "sk-..."
}
}
}
}
Some clients expect command and args separately. This server does not need arguments, so only the command is required.
Local Development Setup
Install dependencies:
uv sync
Run the MCP server from the local checkout:
uv run websearch-mcp
Use this local command in an MCP client while developing:
{
"mcpServers": {
"websearch": {
"command": "uv",
"args": ["run", "websearch-mcp"],
"env": {
"MORPH_API_KEY": "sk-..."
}
}
}
}
Tool Inputs
websearch
Searches the web. By default returns an AI-enriched answer with sources. Pass enrich=false for raw page content.
{
"query": "latest Python 3.13 release notes",
"num_results": 5,
"enrich": true
}
webfetch
Fetches one page and returns compacted markdown.
{
"url": "https://example.com"
}
How It Works
query -> DuckDuckGo HTML -> crawl4ai fetch -> Morph compact -> enriched answer (default)
|
v
raw results + hint (enrich=false)
websearch fetches each result page and compacts its content via Morph. With enrich=true (default), the compacted results are fed to a Morph-powered agent that searches further if needed and synthesizes a final answer with cited sources. With enrich=false, raw compacted results are returned with a hint suggesting enrichment or manual webfetch calls.
When MORPH_API_KEY is not set, the server runs in no-AI mode — content is returned uncompacted with a warning, and enrichment falls back to raw results.
Troubleshooting
If the command is not found, confirm your install location is on PATH:
command -v websearch-mcp
If OpenCode cannot connect, check the configured server status:
opencode mcp list
If requests fail or return uncompressed content, confirm the API key is visible to the server process:
echo "$MORPH_API_KEY"
If browser-based crawling fails on a new machine, reinstall the package and make sure crawl4ai's browser dependencies are available in that environment.
Services Used
| Service | Purpose | Docs |
|---|---|---|
| crawl4ai | Headless crawling and HTML-to-markdown extraction | docs.crawl4ai.com |
| Morph compact | Context compaction for fetched web content | docs.morphllm.com/sdk/components/compact |
| Morph fast models | Agent reasoning for enriched websearch | docs.morphllm.com/sdk/components/fast-models |
License
MIT
Metadata
Release files for morph-websearch-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| morph_websearch_mcp-0.2.0.tar.gz | 5.7 kB | Without provenance | Details for morph_websearch_mcp-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| morph_websearch_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for morph_websearch_mcp-0.2.0-py3-none-any.whl |
Total release size: 11.9 kB
Release files / morph_websearch_mcp-0.2.0.tar.gz
| Download URL | morph_websearch_mcp-0.2.0.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d63507c6035106c6068e5b5dbc924dfe6eb15aee91fb5a199d92bc14a7927a2c
|
|
BLAKE2b-256 checksum How to use checksums |
d708cae91f1fbba81684042cd475a76d44de1c342cf5adfa7ac2af930d7cc792
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Release files / morph_websearch_mcp-0.2.0-py3-none-any.whl
| Download URL | morph_websearch_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
980daa6a4c1a6500449fe803743c1b030e8ca96ec3448a35505c94cee024d900
|
|
BLAKE2b-256 checksum How to use checksums |
d98612281617880e5ad804e88bd73314845fcb9f385a58e0855303a391a3e651
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Security for morph-websearch-mcp 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.