lob-mcp
Related Servers
Alternatives to lob-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that exposes Veil Mail API operations as tools for AI agents, enabling email sending, template management, audience management, and analytics retrieval through natural language.MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server providing tools for DB queries, API calls, file I/O, and text transformations, enabling AI agents like Claude to perform real-world actions.10MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server for Plunk, the open-source self-hosted email platform. Provides 84 tools for transactional email, contacts, campaigns, segments, templates, workflows, events, and analytics through the Plunk API.9419 npm2MIT
- AlicenseAqualityDmaintenanceEnables AI agents to send physical letters and postcards to over 200 countries using Solana cryptocurrency for payment. It provides tools for generating mail quotes, managing wallet balances, and automating physical correspondence directly through the Model Context Protocol.478 npm1MIT
- FlicenseNot gradedqualityDmaintenanceA secure Model Context Protocol server providing HTTP endpoints for AI agent tool execution, including file system operations, shell commands, and LLM-based code generation.1-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to search, read, and send emails with attachment support through the Gmail API. It also provides tools for comprehensive label management and uses secure OAuth2 authentication for mailbox access.295 npmMIT
TDQS
Scored across 78 tools
Resources are cleanly delineated (postcards vs letters vs checks vs creatives vs templates vs template_versions), and the preview/create pairs are explicitly distinguished. Minor overlap exists between lob_*_preview tools and the raw lob_resource_proofs_create, which the description admits calls the same endpoint, plus the bulk verification tools mirror their single-address counterparts.
Nearly every tool follows a predictable lob_<resource>_<verb> pattern (lob_postcards_create, lob_letters_list, lob_webhooks_delete), which is highly readable. A few outliers break the verb convention, e.g. lob_identity_validation (noun-only) and lob_us_verifications_get, but overall consistency is strong.
78 tools is far above what an agent can comfortably navigate and select from, even accounting for the broad Lob API surface. The per-resource list/get/create/cancel pattern is defensible but the sheer volume makes tool selection error-prone and context-heavy.
Coverage is broad: full lifecycle for postcards, letters, self-mailers, checks, templates/versions, campaigns, bank accounts, webhooks, and addresses, plus verifications, QR analytics, and design specs. Minor gaps like no card update/delete exist, but these largely reflect genuine API limitations.