Clover MCP Server

Job search and interview prep MCP. 11 tools, OAuth 2.1, cross-LLM. four-leaf.ai. The clover mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

An open-source Skill that turns Claude (or ChatGPT, Cursor, Codex, GitHub Copilot) into a job search and interview prep coach. It pulls real job postings, role-specific interview intelligence, and resume scoring from the hosted Four-Leaf MCP, then walks the user through preparing for an actual interview.

• Kickoff — the coach figures out what you're prepping for and routes you. Say "help me get ready for my job search"
• Find jobs — natural-language search across 100k+ active postings. Say "find me remote senior data scientist roles"
• Prep for a role — interview pipeline, what to expect, how to win. Say "what's the interview like for a PM at Stripe"
• Practice — calibrated questions with coaching on your answers. Say "give me a few hard system design questions"
• Analyze a JD — scores a resume against a posting and points out gaps. Say "how does my resume stack up against this JD"
• Interview strategy — formats, AI interviewers, work trials, signal vs noise. Say "what are AI interviews actually like"

Its toolset

Everything the assistant can do here goes through one of these:

• four-leaf — coach list show the supported tools and what's detected in the current directory
• Free — the Skill itself, all the data tools in the MCP (jobs, role intel, question bank, match scoring). Daily rate limits on a few of the compute-heavier

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Clover's toolset — four-leaf, Free — is a fair guide to whether it matches your workflow. It is maintained by fourleafai; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the clover mcp server does with a few real requests.