MailOptin

MailOptin Site REST API and MCP Server

The WordPress REST API served by mailoptin.io, plus the Model Context Protocol server exposed through the WordPress MCP Adapter at the mcp namespace. The REST root is a public, self-describing route index — 35 namespaces and 771 routes, each with its argument schema — and content routes under wp/v2 answer anonymously. The MCP endpoint is live but auth-gated, returning 401 mcp_unauthorized with a WWW-Authenticate Bearer challenge that links to RFC 9728 protected-resource metadata. This is the company website's own surface, not a product API for the MailOptin lead-generation service, which ships as a self-hosted WordPress plugin.

GitHub

Documentation

📖
Authentication
https://raw.githubusercontent.com/api-evangelist/mailoptin/refs/heads/main/authentication/mailoptin-authentication.yml
📖
RateLimits
https://raw.githubusercontent.com/api-evangelist/mailoptin/refs/heads/main/rate-limits/mailoptin-rate-limits.yml

Other Resources

🔗
MCPServer
https://raw.githubusercontent.com/api-evangelist/mailoptin/refs/heads/main/mcp/mailoptin-mcp.yml
🔗
OAuthScopes
https://raw.githubusercontent.com/api-evangelist/mailoptin/refs/heads/main/scopes/mailoptin-scopes.yml
🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/mailoptin/refs/heads/main/errors/mailoptin-problem-types.yml
🔗
Conventions
https://raw.githubusercontent.com/api-evangelist/mailoptin/refs/heads/main/conventions/mailoptin-conventions.yml
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/mailoptin/refs/heads/main/apis.yml

API entry from apis.yml

apis.yml Raw ↑ 
aid: mailoptin-site
name: MailOptin Site REST API and MCP Server
description: The WordPress REST API served by mailoptin.io, plus the Model Context Protocol server exposed
  through the WordPress MCP Adapter at the mcp namespace. The REST root is a public, self-describing route
  index — 35 namespaces and 771 routes, each with its argument schema — and content routes under wp/v2
  answer anonymously. The MCP endpoint is live but auth-gated, returning 401 mcp_unauthorized with a WWW-Authenticate
  Bearer challenge that links to RFC 9728 protected-resource metadata. This is the company website's own
  surface, not a product API for the MailOptin lead-generation service, which ships as a self-hosted WordPress
  plugin.
humanURL: https://mailoptin.io/
baseURL: https://mailoptin.io/wp-json
tags:
- WordPress
- Model Context Protocol
- OAuth
properties:
- type: MCPServer
  url: mcp/mailoptin-mcp.yml
- type: Authentication
  url: authentication/mailoptin-authentication.yml
- type: OAuthScopes
  url: scopes/mailoptin-scopes.yml
- type: ErrorCatalog
  url: errors/mailoptin-problem-types.yml
- type: Conventions
  url: conventions/mailoptin-conventions.yml
- type: RateLimits
  url: rate-limits/mailoptin-rate-limits.yml