For providers · MCP
Run your listing from your AI assistant.
Motley speaks the Model Context Protocol — the open standard for connecting assistants to live data and actions. Point any MCP-compatible assistant at your private provider endpoint and manage your listing in plain language. It acts only on your account, and money and identity always come back as a link you open yourself — the assistant never completes payment or verification.
What your assistant can do
The provider tools
Each tool acts only on your account — scoped by the key you generate in your portal.
- begin_self_onboardingStart with no account at all — give your business name and email and we send a one-time link. Open it to get the access key you paste back into your assistant. Controlling the inbox is the proof.
- onboarding_statusSee exactly where your listing stands and the one thing keeping it from going live — no account, identity pending, not subscribed, or live.
- list_listing_vocabularyPull the canonical listing vocabulary — grade bands, session formats, subject and specialty suggestions, admission goals, the NYC school-district map — to draft a valid listing.
- validate_listingCheck a drafted listing against our schema before saving — get the normalized version back, or per-field fixes.
- submit_listingSave your listing as a draft. It stays private until you pass identity verification and hold an active subscription.
- get_kyc_linkGet a secure Stripe Identity link to verify your identity. The assistant hands you the link — it never sees your ID.
- get_subscription_linkGet a Stripe Checkout link for the flat listing subscription, monthly or annual. You finish payment in Stripe — never the assistant.
How to connect
Three steps to a connected assistant.
- 01
Get listed — or start from scratch
Log in to create your provider account. Or, with no account at all, have your assistant call begin_self_onboarding with just your name and email — we email a one-time link that hands you an access key.
- 02
Generate a key
In your portal under Settings → MCP access, generate a bearer key. It's shown once, and it scopes every action to your own account.
- 03
Point your assistant at your endpoint
Add your private provider endpoint as a remote MCP server with the key as the Bearer token. Then draft your listing, check what's between you and going live, and finish verification and billing — in plain language.
Connect it
Point your client at your endpoint.
The same wiring as any remote MCP server — with a key so it only ever touches your account.
Most MCP clients connect one of two ways — either works. Your private endpoint always needs a key (the Authorization header), so the server knows it's you and scopes every action to your account.
Your endpoint (find the real value in your portal once you log in):
<your-provider-endpoint>In a client with native remote-MCP support, open Settings → Connectors, add a custom connector, paste your endpoint, and set an Authorization header to Bearer <your key> — the provider tools appear, no restart required.
On a client that only loads servers over stdio through a config file (like Claude Desktop), bridge to the same endpoint with mcp-remote. Add this to your claude_desktop_config.json and restart — replacing YOUR_PROVIDER_KEY with the key you generated:
{
"mcpServers": {
"motley-provider": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"<your-provider-endpoint>",
"--header",
"Authorization: Bearer YOUR_PROVIDER_KEY"
]
}
}
}Treat the key like a password — it can edit your listing. You can revoke it any time in Settings → MCP access.