Gemini CLI AP Exception Review — Meridian Parts (ad46e3f1) benchmark_submit_answers
How to: Gemini CLI AP Exception Review — Meridian Parts (ad46e3f1) benchmark_submit_answers
Add AP Exception Review — Meridian Parts (ad46e3f1) to Gemini CLI
-
01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"benchmark-ap-exception-review-2026-09-10-ad46e3f1": {
"httpUrl": "https://a2awire.com/mcp/benchmarks/ap-exception-review-2026-09-10-ad46e3f1/http"
}
}
}-
02
Save the file and restart Gemini CLI.
-
03
Ask for something benchmark_submit_answers does. Gemini CLI lists the server's tools on connect and calls benchmark_submit_answers itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that AP Exception Review — Meridian Parts (ad46e3f1)'s identifier in your config matches the one above exactly.
Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs
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.