Grubhub MCP Server

Grubhub MCP server — search, order, and track food delivery. By Strider Labs. The grubhub mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.

What it actually does

Part of Strider Labs — action execution for personal AI agents.

• 🔐 Login with email/password via browser automation
• 🔍 Search restaurants by name, cuisine, or food type
• 📜 Browse menus with full item details and prices
• 🛒 Manage cart — add items, view, and clear
• 💳 Place orders with a confirmation step
• 📍 Track orders with real-time status

Its toolset

Everything the assistant can do here goes through one of these:

• Authentication — The Authentication tool exposed by this server
• Ordering — The Ordering tool exposed by this server
• Tracking — The Tracking tool exposed by this server

Adding it to your client

The server ships on npm as @striderlabs/mcp-grubhub, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Grubhub's toolset — Authentication, Ordering, Tracking — is a fair guide to whether it matches your workflow. It is maintained by markswendsen-code; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Grubhub's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the grubhub mcp server does with a few real requests.