About this integration
MCP server for OpenTable - let AI agents book restaurant reservations and manage dining autonomously
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.2
- Package
- @striderlabs/mcp-opentable
- Last compatibility test
- Not independently tested
Connect your agent
@striderlabs/mcp-opentablePublisher documentation describes persistent account sessions and browser automation. The password, session, token-refresh, and MFA flow does not fit one native authentication label, so authentication remains unknown. The package and OpenTable connection were not executed or independently security-audited.
Capabilities: Search restaurants, Check reservation availability, Create and manage reservations
Connected profiles
Additional details
io.github.markswendsen-code/opentable
Source ↗ · Checked 2026-09-170.1.2
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17OPENTABLE_EMAIL, OPENTABLE_PASSWORD
Source ↗ · Checked 2026-09-17@striderlabs/mcp-opentable
Source ↗ · Checked 2026-09-190.1.5
Source ↗ · Checked 2026-09-19Publisher documentation says account sessions persist across process restarts; the documented MCP client configuration launches the Node package as a local child process.
Source ↗ · Checked 2026-09-19Publisher documentation describes encrypted persistent credentials, OAuth token refresh, and SMS/email MFA. This mixed password/session mechanism is outside the native authentication taxonomy; account credentials may be configured.
Source ↗ · Checked 2026-09-19The documented MCP client configuration launches @striderlabs/mcp-opentable with npx; the existing listing's local stdio connection shape is retained.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19