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.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/mailoptin-site"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

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
- MCP
- Authentication
tags_raw:
- 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