Take the OAuth path where your client supports it — you approve which projects the integration may touch, and revoke it from the same admin page. Destructive operations ask first: deletes, full block replacements, URL structure changes and script overwrites all prompt for confirmation. Rate limits are per plan, 60 requests a minute on Growth and 300 on Pro, which is why bulk imports should go through the bulk tool rather than a loop.
The management interface for a Listable directory site, exposed as tools. Every site-management operation — listings, taxonomy, page blocks, forms, settings — is callable, so building a directory becomes something you describe rather than click through.
- ~47 tools grouped by area, covering projects, items, categories, custom fields, pages and blocks, forms, settings, redirects and uploads
- Listings with full CRUD plus `bulk_create_items`, which takes up to 100 listings in a single call
- Categories with trees and conflict inspection; custom fields in text, number, date, url, checkbox, select, phone, address and image types
- Page blocks and global block areas — homepage hero, homepage main, detail page, category pages
- Settings for the menu, scripts, SEO and URL structure, plus image and file uploads for use in listings and pages
- `get_schema` is called first by design, so edits use your site's real custom fields and block types
Two routes. If your client speaks HTTP MCP, add `https://app.get-listable.com/api/v1/external/mcp` and log in through OAuth — Claude Code takes `claude mcp add --transport http`; access tokens last 1 hour and refresh silently for 1 month. For stdio-only clients such as Claude Desktop, install the npm package listable-mcp, version 0.1.1, run it as `npx -y listable-mcp`, and set `LISTABLE_API_TOKEN` to a key created in your Listable admin. `LISTABLE_MCP_URL` overrides the upstream endpoint for self-hosted or staging setups.
One command plus a key — npx -y listable-mcp, then supply credentials