Use Desearch web search with FastMCP
Tested 17 November 2026.
For Python developers who want to call Desearch tools from a FastMCP client. This example starts the pinned Desearch MCP server as a local stdio subprocess, discovers web-search, and makes one real search request.
Tested versions: FastMCP 4.2.0; MCP SDK 2.3.0. Desearch MCP server: 0.3.3.
Before you begin
Use Node.js 24.16.0, Python 3.12.13 and uv 0.12.1. These examples were tested on macOS with Apple Silicon on 17 November 2026. You need a Desearch API key with available credits, and network access to the npm and Python package registries and Desearch. Set DESEARCH_API_KEY in your shell using your secret manager before running the example. Keep it out of source files.
Desearch API requests use your account credits. Check Desearch pricing for current rates. This example calls the web-search tool once. Search titles and links can change between runs.
Keep the accompanying assets folder beside this guide. Run the commands in that directory. The package lock fixes Desearch MCP server 0.3.3 and its npm dependencies. The Python lock fixes the tested dependency set.
Download the assets
Save these files in an assets folder in your working directory, keeping the paths shown:
assets/desearch-mcp-server/package-lock.jsonassets/desearch-mcp-server/package.jsonassets/fastmcp.lock
Install the pinned dependencies
Run a search
Save this as fastmcp_search.py in the same directory:
Run it with your API key already present in the environment:
A successful run prints JSON containing a nonempty title and link. The test returned Our Documentation | Python.org. The returned link began with /go/v1/; treat it as a Desearch redirect path, rather than a canonical source URL. The response order and redirect token can change. The example stops its child processes on exit.
Troubleshooting
A missing DESEARCH_API_KEY environment variable stops the example before a search. Starting the stdio Desearch server directly without it produces DESEARCH_API_KEY environment variable is required and a nonzero exit. HTTP discovery can succeed without credentials: tools/list returned 200, while an unauthenticated tools/call returned HTTP 401 with isError: true and instructions to send a bearer token or x-api-key. Successful discovery alone does not prove search access. For a rejected key or insufficient credits, verify the key and account balance before retrying.
If the client cannot import FastMCP, rerun the lock installation in the same .venv. If web-search is absent, confirm the server package and local path match this example.