Zed openfda mcp server openfda_dataframe_describe
How to: Zed openfda mcp server openfda_dataframe_describe
Add openfda mcp server to Zed
-
01
Open ~/.config/zed/settings.json and merge this in. Keep any servers already there.
{
"context_servers": {
"openfda-mcp-server": {
"url": "https://openfda.caseyjhand.com/mcp"
}
}
}-
02
Save the file and restart Zed.
-
03
Ask for something openfda_dataframe_describe does. Zed lists the server's tools on connect and calls openfda_dataframe_describe itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that openfda mcp server's identifier in your config matches the one above exactly.
Merge this into your existing settings object — do not replace the file. Zed docs
Set these first
openfda mcp server will not start until these are set, so openfda_dataframe_describe never becomes available.
-
OPENFDA_API_KEY -
OPENFDA_MIRROR_ENABLED -
OPENFDA_MIRROR_PATH -
OPENFDA_MIRROR_REFRESH_CRON -
OPENFDA_MIRROR_FALLBACK_LIVE -
OPENFDA_MIRROR_REFRESH_TIMEOUT_MS -
OPENFDA_MIRROR_BASE_URL -
MCP_LOG_LEVEL
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.