MCP Recipes
pro+ onlyConnect an MCP Client
Point an MCP-compatible agent or IDE at the LLM Prover server and confirm the tool list loads.
Run it -- paste into your MCP agent
Highlighted parts are placeholders -- replace them with your own values before (or after) copying.
List all the tools available on the LLM Prover MCP server and give me a one-line summary of what each one does, grouped by what they operate on (comparisons, evaluations, benchmarks, RAG stores, and so on).
Goal
Connect an MCP client to the LLM Prover server and confirm it can see the available tools.
When to use
Run this once per client (VS Code, Claude Desktop, Cursor, Amazon Q, or any
Streamable-HTTP client) before you try to run any other recipe. If tools/list
comes back empty or errors, every downstream recipe will fail, so verify the
connection here first.
Steps
- Copy the endpoint. Open the MCP page in the dashboard and copy the endpoint URL from the Endpoints tab.
- Pick your client config. On the Clients tab, copy the config snippet for your client. IDE clients (VS Code, Cursor, Claude Desktop) use OAuth – a browser login opens automatically. Programmatic clients (Amazon Q, scripts) use a developer API key as a Bearer token.
- Add the server. Paste the snippet into your client’s MCP config and reload the client so it picks up the new server.
- List the tools. Ask the agent to list the MCP tools, or call
tools/listdirectly. A populated list means the connection and auth both work.
Verification
- The client shows the server as connected (no auth or discovery errors).
tools/listreturns a non-empty set of tools.
Where this leads
Natural next recipes once you are comfortable with this one.