pro.makeup MCP server

Hosted Model Context Protocol server for the pro.makeup directory — 214,000+ certified makeup professionals (artists, salons, schools, shops, and brands) across 100+ countries.

This repository is the public specification and integration kit for the hosted MCP server at https://pro.makeup/api/mcp. The server itself is operated by PRO Makeup / Evergrow Management PTE LTD; this repo collects the server card, OpenAPI spec, example client configurations, registry submission metadata, and architectural documentation.

If you are building an agent that needs to find a makeup professional, school, or shop — point your MCP-aware client at the URL above and you're done.

Quick start

Claude Desktop / Claude Code

Add to your claude_desktop_config.json (Claude Desktop) or per-project .mcp.json (Claude Code):

{
  "mcpServers": {
    "promakeup": {
      "type": "streamable-http",
      "url": "https://pro.makeup/api/mcp"
    }
  }
}

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "promakeup": {
      "url": "https://pro.makeup/api/mcp"
    }
  }
}

Raw HTTP (`curl`)

curl -s -X POST https://pro.makeup/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

See examples/ for additional configurations.

What it exposes

8 tools, 3 prompts, 2 templated resources. All read tools require no authentication; the two phone-related / write tools require a scoped Bearer token (see spec/auth.md).

Tool	Scope	Read-only?
`promakeup_search_pros`	open	✅
`promakeup_get_business_by_slug`	open	✅
`promakeup_get_business_by_phone`	`owner:read`	✅
`promakeup_get_business`	open	✅
`promakeup_list_services_nearby`	open	✅
`promakeup_list_schools`	open	✅
`promakeup_get_discovery_summary`	open	✅
`promakeup_emit_listing_event`	`listing-events:write`	❌

Prompts: find_makeup_pro, compare_pros, book_appointment_intent.

Resources: promakeup://business/{slug}, promakeup://category/{category}/featured.

Full tool descriptions, input schemas, and example outputs are in spec/server-card.json and spec/openapi.json.

Auth

Tokens are issued out-of-band by the operator. Email support@pro.makeup with:

The integration name and use case
The scopes you need (the smallest subset that works)
The expected request volume

Full token format, lifecycle, and error responses in spec/auth.md.

Repository layout

.
├── README.md                — this file
├── LICENSE                  — MIT
├── server.json              — MCP registry (registry.modelcontextprotocol.io) submission
├── smithery.yaml            — Smithery.ai integration manifest
├── spec/
│   ├── server-card.json     — SEP-1649 MCP server card
│   ├── agent-card.json      — A2A protocol descriptor
│   ├── openapi.json         — OpenAPI 3.1 spec for the underlying HTTP API
│   ├── auth.md              — Bearer-token authentication model
│   ├── agents.md            — agent-oriented integration guide
│   ├── llms.txt             — llms.txt manifest (short)
│   └── llms-full.txt        — llms-full.txt reference (comprehensive)
├── examples/
│   ├── claude-desktop.json  — Claude Desktop MCP config
│   ├── cursor.json          — Cursor MCP config
│   ├── vscode.json          — VS Code (mcp-aware extensions) config
│   ├── curl-quickstart.sh   — bash smoke tests
│   └── typescript-client.ts — minimal TypeScript client over JSON-RPC
└── docs/
    ├── architecture.md      — design of the hosted MCP server
    └── registry-submission.md — registry submission tracker

Listings

This MCP server is registered in:

Registry	Status	Link
registry.modelcontextprotocol.io (official)	live	`makeup.pro/mcp`
PulseMCP	auto-ingests from official	expected within 7 days
Glama	auto-ingests from official	expected within 1-3 days
MCP Now	auto-ingests from official	expected within days
Smithery.ai	manual submission needed (GitHub OAuth)	—
mcp.so	manual submission needed	see `docs/registry-submission.md`

Reporting issues / requesting changes

Bug or behavioral issue with a tool: open a GitHub issue
Inaccuracy on a specific business listing: report via the listing's "Report this listing" link on pro.makeup, or email support@pro.makeup
Security issues: email support@pro.makeup directly (do not file a public issue)

License

MIT — see LICENSE. The pro.makeup directory data itself is © PRO Makeup / Evergrow Management PTE LTD; the data's usage policy is declared in the site's robots.txt via the Content-Signal directive (search=yes, ai-train=yes, ai-input=yes).

Operator

Operated by Evergrow Management PTE LTD. Contact support@pro.makeup.

pro.makeup