PeoplePerHour MCP Server
Search projects, freelancers and Offers on PeoplePerHour, read briefs and profiles, keep a watchlist and saved searches.
Servidor MCP hospedado
npx add-mcp 'https://cotlet.dev/mcp/v1/peopleperhour'Instala no Claude Code, Codex, Cursor e outros
Documentação
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
PeoplePerHour API and MCP server: Let your AI agent run your PeoplePerHour project hunt.
PeoplePerHour's own AI is Phoenix, a chat on peopleperhour.com that helps buyers find freelancers. There is no public API, MCP server or webhook for your own agent (checked 24 Oct 2026), so Cotlet runs 17 PeoplePerHour tools hosted, over MCP and REST.
Find open PeoplePerHour projects and read their briefs through MCP or REST. Build a shortlist with your AI agent, n8n, Make, Zapier or a script; send proposals yourself.
- Free 7-day trial, no card
- Unofficial, not affiliated with PeoplePerHour
- Page: https://cotlet.dev/integrations/peopleperhour-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by PeoplePerHour. PeoplePerHour is a trademark of its owner. If PeoplePerHour's own integrations cover what you need, use them first.
What can you automate in PeoplePerHour?
- Find new projects in your skills
- Read a brief before you bid
- Keep saved search alerts
- Shortlist freelancers by rate and reviews
- Compare Offers before you buy
- Check notifications and WorkStreams
Does PeoplePerHour have an MCP server or an API?
- Saved Searches are the only built-in alert: up to 10 per account, each an email, instant or daily. Nothing in them can be called from code.
- An API with app keys existed around 2014. Its PHP client was last updated in March 2015, and api.peopleperhour.com now opens the website.
- Zapier, Make and n8n have no PeoplePerHour app. Apify scrapers read public job listings for $1 to $4 per 1,000 results.
| What you need | Saved search email | Apify scraper | Cotlet |
|---|---|---|---|
| New projects in your skills | Email, instant or daily | Public listings | Since your last check |
| Full brief, attached files, buyer questions | No | Some fields | Yes |
| Freelancer profiles and Offers | No | Separate actors | Yes, in 17 tools |
| Your projects, notifications, WorkStreams | No | No | Yes, as you |
| Fixed for you when PeoplePerHour changes | Yes | By the actor author | Yes |
Checked 24 Oct 2026. Sources: PeoplePerHour: How it works for freelancers, PeoplePerHour Help: Submitting Proposals, PeoplePerHour Help: Saved Searches, PeoplePerHour: Terms of website use, PeoplePerHour: Phoenix, PeoplePerHour/pph-php-client, Apify: PeoplePerHour actors
How does Cotlet connect to PeoplePerHour?
- Log in to PeoplePerHour. Once. A free buyer account works.
- Choose MCP or REST. Connect an AI agent or create a Cotlet API key.
- Run your workflow. Ask your agent or call the REST API.
We never save your password, and no tool sends a proposal, a message or a payment.
Connect PeoplePerHour to your AI agent or workflow
Use MCP with ChatGPT, Claude, Cursor or Codex, or authenticated HTTP in n8n, Make or Zapier. The REST guide follows the agent setup.
- Enable PeoplePerHour for agents. Sign up, log in to PeoplePerHour in its Cloud Browser, then press Enable for agents.
- Add the PeoplePerHour address. Put https://cotlet.dev/mcp/v1/peopleperhour in the MCP or connector settings of your agent.
- Sign in or paste a key. Chat apps sign you in to Cotlet. Editors and scripts use an API key from the console.
Already on https://cotlet.dev/mcp/v1? It carries PeoplePerHour too. Enabled it later? Refresh the connector so the new tools show up.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-peopleperhour \
https://cotlet.dev/mcp/v1/peopleperhour \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet-peopleperhour": {
"url": "https://cotlet.dev/mcp/v1/peopleperhour",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-peopleperhour]
url = "https://cotlet.dev/mcp/v1/peopleperhour"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: peopleperhour_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: peopleperhour_read
How to use the PeoplePerHour REST API
Create your Cotlet API key
Sign in to your PeoplePerHour account in its Cotlet Cloud Browser and enable the app for agents. A free buyer account works.
Create a Cotlet API key scoped to PeoplePerHour with read access. Store it in your environment as COTLET_API_KEY.
Make your first PeoplePerHour API request
cURL: search_projects:
curl "https://cotlet.dev/api/v1/peopleperhour/projects/search?query=web+design&limit=20" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read project matches and continue the search
A successful REST call puts the tool output in result. This illustrative example excerpt omits call IDs, messages and credit details.
Example response excerpt:
{
"status": "success",
"app": "peopleperhour",
"tool": "search_projects",
"result": {
"projects": [
{
"project_id": "4527860",
"title": "Website design",
"budget": {
"amount": 70,
"currency": "EUR",
"type": "fixed_price"
},
"proposals": 42,
"posted_at": "2026-10-22T08:22:55Z"
}
],
"next_cursor": null
}
}
Read result.projects. The maximum limit is 50.
Pass next_cursor unchanged as cursor until null: it can contain a page and index such as 1.20, so do not parse or increment it yourself.
For scheduled searches, since means strictly posted after that time. A timestamp without a timezone is interpreted as UTC.
With since, one call scans at most 200 newest results; a short result may still have a cursor. Finish pagination before advancing your saved checkpoint.
The newest ordering is not strictly by posting time.
Budgets are in the buyer currency. An hourly budget is a rate per hour.
Use get_project with a returned project_id or project URL for the full brief, attachments and current open status. Private, removed or moderated projects may be unavailable even with a valid session.
The tools send no proposals, messages, hires or payments. Prepare a shortlist and send proposals yourself.
For polling, choose an hourly or two-hourly cadence rather than checking every minute.
PeoplePerHour workflows with n8n, Make and Zapier
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Search your chosen project keywords on your own schedule and deliver a shortlist through your configured email step. |
| Make | HTTP > Make a request | Filter by budget currency and proposal count, then read selected full briefs for human review. Do not compare amounts across currencies without your own conversion step. |
| Zapier | Webhooks by Zapier > GET or Custom Request | Compare project IDs plus proposal counts and open status using project details; deliver changes to your chosen destination. No proposal is sent. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record or state comparisons.
Cotlet reads the source; your workflow steps write to the chosen destination. These are configured HTTP workflows, not native Cotlet connectors or prebuilt templates.
Remember handled IDs to avoid duplicates and compare current state to detect changes to existing records. Python or Node.js can use the same HTTP calls without an AI agent or a required SDK.
The API and MCP reference lists methods, paths and inputs. The REST API guide covers request format, errors and approvals.
PeoplePerHour API endpoints and MCP tools
Projects and budgets
Budgets come in the buyer's currency; with a since time, one search scans the 200 newest projects.
- Search projects (
search_projects, read): Open projects buyers posted, newest first, with budget, category, proposals and the brief's start. - Get project (
get_project, read): One project's full brief with budget, attachments, interview questions, buyer and proposal count. - List my projects (
list_my_projects, read): Projects this account posted as a buyer, with status, budget and proposal count. - List categories (
list_categories, read): The 10 project categories with their subcategories and typical budgets per freelancer level.
Watchlist and saved searches
The only writes, all on your own account. Editing a saved search changes its name and email only.
- Watch project (
watch_project, write): Add a project to this account's watchlist (Favourite Jobs) to come back to it later. - Unwatch project (
unwatch_project, write): Take a project off this account's watchlist. - List watchlist (
list_watchlist, read): Open projects on this account's watchlist (Favourite Jobs), with budget and proposal count. - List saved searches (
list_saved_searches, read): This account's saved project searches with their filters and email alert setting. - Save search (
save_search, write): Save a project search with an email alert, or rename one or change how often it emails. - Delete saved search (
delete_saved_search, write): Delete one of this account's saved project searches and its email alert.
Freelancers and Offers
Rates and Offer prices in your account currency. A profile brings the reviews on its first page.
- Search freelancers (
search_freelancers, read): Freelancers by skill or keyword, with rate, rating, reviews, completed projects and skills. - Get freelancer (
get_freelancer, read): A freelancer's public profile: rate, stats, skills, portfolio and the latest reviews on the page. - Search Offers (
search_offers, read): Fixed-price Offers freelancers sell, by keyword or price, with sales, rating and seller. - Get Offer (
get_offer, read): One Offer with its full description, what the seller needs from you, prices, add-ons and images.
Your account
Each WorkStream comes with its last message, not the whole thread.
- Get account (
get_account, read): The signed-in PeoplePerHour account: name, type, buyer stats, unread messages and favourite counts. - List notifications (
list_notifications, read): The latest notifications of this account (proposals, messages, project updates) and unread counts. - List WorkStreams (
list_workstreams, read): This account's WorkStreams (conversations with hired freelancers) with the last message.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/peopleperhour-api-mcp-server#tools
Who can see my PeoplePerHour session, and how do I revoke it?
- What we store. The PeoplePerHour profile you logged in to, AES-256-GCM, in Finland. No password.
- What your agent gets. 17 PeoplePerHour tools. Never the session cookie.
- What stays shut. Your email, password, security question and payment settings. No tool opens them.
- What we log. Time, tool and status per call. Briefs and profiles are not kept.
- When the session ends. PeoplePerHour keeps you in for about 100 days. Then we email you a link to log in again.
- How to cut access. Disable for agents, reset the browser or delete the key. It stops at the next call.
A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Searches since the last run. One search per skill, with since set.
- Cuts on numbers. Below your budget or too many proposals: out.
- Reads the briefs left. Deliverables, files, the buyer's questions.
- Hands you the shortlist. No longer than your credits. You bid.
None of the 17 tools waits for approval, because none reaches another person. The 4 writes touch your watchlist and saved searches, and a buyer is not told when you watch a project.
| Action | Undo |
|---|---|
| Delete a saved search | No, save it again with its filters |
| Rename a search, change its alert | Yes, save_search again |
| Watch, unwatch a project | Yes, the other tool |
Scripts get the same tools under /api/v1/peopleperhour, with one key and one price. A failed call costs nothing. The tools table lists the REST path of each tool.
See the REST API guide for a first read request and workflow examples.
How much does the PeoplePerHour API and MCP server cost?
About $23 a month for a freelancer checking two skills every day, 3,940 credits.
| Job | Calls | Credits |
|---|---|---|
| Search new projects for 2 skills, daily | 2 × 30 | 600 |
| Read the briefs that pass, daily | 3 × 30 | 900 |
| Check watched projects, daily | 1 × 30 | 300 |
| Notifications and WorkStreams, daily | 2 × 30 | 600 |
| Median budgets in your category, weekly | 1 × 4 | 40 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 3,940 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- One-time packs, valid 12 months, no subscription
Web design got 1 to 2 new projects a day on 24 Oct 2026, so 3 briefs a day covers two skills. Dollars at the $29 pack rate. No Proposal credits are spent.
PeoplePerHour MCP server, scrapers or job monitors: which to use
| Option | What it does | Where it stops |
|---|---|---|
| GitHub | No community PeoplePerHour MCP server found. A few job scrapers with 0 stars. | The official PHP client is for an API last updated in 2015. |
| Apify job scrapers | The largest has 138 users: public job listings at $4 per 1,000 results. | Not signed in: no files, watchlist, notifications or WorkStreams. |
| Vollna | Job monitor for Upwork, Freelancer and PeoplePerHour, from $16 a month. | Built around Upwork; no MCP server found. |
| n8n template 7782 | Jobs from four marketplaces with AI proposals in Google Sheets. | You host and fix it; it reads feeds, not briefs. |
Pick a scraper for bulk market data on public jobs. Pick Cotlet to check projects signed in as you, through an agent, a script or HTTP steps in your automation platform.
Run our PeoplePerHour MCP server on your own computer
The 17 PeoplePerHour tools are public on GitHub too, as a Python MCP server and REST API. Run them with your own Chrome, try them on your account and read how each one talks to PeoplePerHour. It is a trimmed copy of what runs on cotlet.dev, free to use in your own business.
- Free for personal use, learning and testing
- Works while your computer is on, logged in through your own Chrome
- When PeoplePerHour changes, you update it
- License Elastic 2.0: free in your own business; ChatGPT, your phone and 24/7 runs need hosted Cotlet
- Code: https://github.com/cotletdev/peopleperhour-api-mcp-server
Who runs Cotlet
Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), working since 2019. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the PeoplePerHour tools go to contact@cotlet.dev.
PeoplePerHour MCP server: questions
Can I use the API without an AI agent?
Yes. Use a script or HTTP workflow with your Cotlet API key. No MCP connection is required. Sign in to your app account in its Cloud Browser first.
Can I use PeoplePerHour with n8n, Make or Zapier?
Yes. Configure authenticated HTTP requests with your Cotlet API key. You choose the schedule and destination steps; see the REST API guide on this page.
How do I start?
Sign up free at https://cotlet.dev, open PeoplePerHour under Integrations in the console and log in to PeoplePerHour in its Cloud Browser. The trial starts with your Cotlet account, no card.
How do I connect PeoplePerHour to ChatGPT or Claude?
Sign up at cotlet.dev, log in to PeoplePerHour once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your PeoplePerHour account through Cotlet, in their phone apps too.
What can ChatGPT do in PeoplePerHour?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in PeoplePerHour: find new projects that match my skills; read a project brief before writing a proposal; watch for urgent projects in a category. You ask in plain words, and anything that reaches other people waits for your OK first.
Do I need a paid PeoplePerHour plan?
No. Any PeoplePerHour account works, and a free buyer account is enough. The tools read projects, freelancers, Offers and your own account, and change only your watchlist and saved searches, so you need no freelancer subscription and spend no Proposal credits.
What can it not do yet?
It does not post or edit projects, send or cancel proposals, send messages, invite, shortlist or hire freelancers, favourite Offers or freelancers, or pay. It does not list the proposals on your own projects, read whole WorkStream conversations (only the last message), list one freelancer's Offers, or page past the reviews on a profile's first page. Freelancer features (proposals, Offers of your own, invoices, Proposal credits) need a freelancer account with a paid PPH Basic subscription that PeoplePerHour moderates. get_project returns no list of skills, because PeoplePerHour's project data has none; the skills are in the brief text.
What does it change on my PeoplePerHour account?
Only your watchlist (watch_project, unwatch_project) and your saved searches (save_search, delete_saved_search). The buyer is not told when you watch a project, and saved search alerts go to your own email. A saved search keeps its filters: save_search can rename it or change its alert, and other filters need a new search. PeoplePerHour allows 10 saved searches per account.
Whose currency are prices in?
Project budgets are in the buyer's currency and freelancer hourly rates in the freelancer's. Offer prices and the hourly_rate and price_range filters use your account currency; get_offer also lists every currency the seller set. list_categories gives median budgets in GBP, USD or EUR.
Does PeoplePerHour have webhooks or an RSS feed?
Neither, as of 24 Oct 2026. The only alert is a saved search email. To react to new projects, run your agent on a schedule with search_projects and a since time.
Is the MCP server different from the REST API?
No, only the door differs. Both carry the same 17 tools and answers, one key and one price. Agents use MCP; cron jobs and HTTP steps use REST.
What happens to my data if I leave?
Reset browser deletes your PeoplePerHour profile on our side, and closing your Cotlet account removes the browser too. Unused credits stay valid 12 months from purchase.
Is Cotlet affiliated with PeoplePerHour?
No. Cotlet is independent and not affiliated with People Per Hour Ltd.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.