PeoplePerHour by Cotlet

dev.cotletPublished by cotlet.devOfficial publisherv1.0.2Updated Oct 29, 2026

Search projects, freelancers and Offers on PeoplePerHour, read briefs and profiles.

The publisher's own server: Cotlet

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Reads PeoplePerHour through your own account: search projects, freelancers and Offers, read briefs and profiles, and manage your watchlist and saved searches.

What you can do
  • Search and read projects: open projects with budget and proposal counts, full briefs with attachments and interview questions, and projects you posted as a buyer
  • Search and read freelancers and Offers: profiles with rates, skills and recent reviews, and fixed-price Offers with prices and add-ons
  • Manage your watchlist: list, add and remove projects you follow
  • Manage saved searches: list, save, rename or delete searches and their email alerts
  • Read your account: profile and buyer stats, notifications with unread counts, WorkStreams with the last message
  • Look up categories with subcategories and typical budgets per freelancer level
When to use it
Useful when you want an assistant to shortlist PeoplePerHour projects or freelancers, read briefs before writing a proposal, compare Offers, or keep a watchlist and email alerts without browsing the site by hand.
Requirements
Runs locally with Python 3.11 or newer and Google Chrome signed in to PeoplePerHour, or as a remote endpoint at cotlet.dev with an Authorization header carrying a Cotlet API key. The local version reads your PeoplePerHour cookies from Chrome via remote debugging, or takes the session cookie through PEOPLEPERHOUR_AUTH_TOKEN. A free PeoplePerHour account is enough.
Before you install
The local session file holds PeoplePerHour cookies: anyone with it can act as you, so keep it out of git and shared folders. Four tools write to your account (watchlist and saved searches); a watched project lists you among its watchers. It cannot send proposals or messages or spend credits, and it is licensed for noncommercial use only. Heavy polling may get your account rate-limited or blocked.

Installation

In SourceWeft

  1. Open PeoplePerHour by Cotlet in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.cotlet%2Fpeopleperhour/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "peopleperhour-by-cotlet": {
      "type": "http",
      "url": "https://cotlet.dev/mcp/v1/peopleperhour/connect"
    }
  }
}

README

PeoplePerHour API and MCP server, self-hosted

A PeoplePerHour API and a PeoplePerHour MCP server you run on your own computer, in Python, on the session of your own Google Chrome. The same 17 PeoplePerHour tools we run in production at Cotlet: search open projects and read full briefs, search freelancers and Offers and read profiles with recent reviews, keep a project watchlist and saved searches with email alerts, see median budgets per category, and read your own posted projects, notifications and WorkStreams.

PeoplePerHour has no public API and no official MCP server. This repo gives you both:

  • MCP server for Claude Code, Claude Desktop, Cursor, Codex and any MCP client, over stdio or HTTP. Setup
  • REST API on http://127.0.0.1:8787/api/v1/peopleperhour, with OpenAPI docs at /docs. Setup
  • Python: call("search_projects", query="web design"), plus 9 ready scripts in examples/.

13 tools read. The other 4 change only your own watchlist and saved searches. Nothing here sends a proposal or a message, posts a project, buys an Offer or pays, and no Proposal credit is spent.

It is for technical people who want to run it themselves, for noncommercial use only (license). If you want it running 24/7 on a server, kept working when PeoplePerHour changes its site, for a team or a business, use the hosted version at cotlet.dev.

[PeoplePerHour MCP server] [Python 3.11+] [License: PolyForm Noncommercial 1.0.0] [MCP Badge]

bash
uv tool install peopleperhour-api-mcp                  # or: pip install peopleperhour-api-mcppeopleperhour-mcp connect                          # reads your PeoplePerHour session from Chromepeopleperhour-mcp call search_projects query="web design" limit=5claude mcp add peopleperhour -- uvx peopleperhour-api-mcp mcp

Contents

How it works

text
AI agent (MCP) / script (REST, Python) ──▶ peopleperhour-mcp on your computer ──your cookies──▶ www.peopleperhour.com                                                    ▲                      peopleperhour-mcp connect ────┘ reads them once from your Chrome (DevTools Protocol)
  1. You sign in to PeoplePerHour in your own Chrome, the way you always do. Tick Remember me.
  2. peopleperhour-mcp connect attaches to that Chrome through the Chrome DevTools Protocol, reads the peopleperhour.com cookies and saves them to ~/.config/peopleperhour-api-mcp/session.json, readable by your user only. It never sees or stores your password.
  3. Every tool call is a request to the JSON API the PeoplePerHour site itself calls (www.peopleperhour.com/v2/...) with those cookies, sent with curl_cffi, which copies Chrome's TLS fingerprint. No headless browser runs.

The session lives in the api cookie, about 100 days after a sign-in with Remember me. When PeoplePerHour signs you out, the server reads the cookies from Chrome again, if Chrome is open with remote debugging on.

Requirements

  • Python 3.11 or newer.
  • Google Chrome 144 or newer, signed in to PeoplePerHour. Any Chrome or Chromium works with a debugging port.
  • macOS, Linux or Windows.
  • Any PeoplePerHour account. A free buyer account is enough for all 17 tools.

Install

From PyPI:

bash
uv tool install peopleperhour-api-mcp       # or: pipx install peopleperhour-api-mcp, or: pip install peopleperhour-api-mcppeopleperhour-mcp --version

MCP clients can also run it with no install: uvx peopleperhour-api-mcp mcp.

From source:

bash
git clone https://github.com/cotletdev/peopleperhour-api-mcp-server.gitcd peopleperhour-api-mcp-serverpython3 -m venv .venv. .venv/bin/activate              # Windows: .venv\Scripts\activatepip install -e .peopleperhour-mcp --version

With uv: uv venv && uv pip install -e ., then uv run peopleperhour-mcp ....

Setting it up with an AI agent (Claude Code, Codex, Cursor)? Open it in this folder and ask it to set up the repo: AGENTS.md tells it every step, and it asks you only for the steps in Chrome.

To update: uv tool upgrade peopleperhour-api-mcp (or pip install -U peopleperhour-api-mcp), from source git pull && pip install -e .. We copy every change of the hosted PeoplePerHour tools into this repo.

Connect your Chrome

Option A: your everyday Chrome (recommended)

  1. Open chrome://inspect/#remote-debugging in Chrome and switch remote debugging on. Chrome then accepts DevTools connections from programs on this computer, and asks you before each one.

  2. Make sure you are signed in at peopleperhour.com.

  3. Run:

    bash
    peopleperhour-mcp connect
  4. Chrome asks whether to allow the connection. Click Allow.

text
Saved 9 PeoplePerHour cookies to /Users/you/.config/peopleperhour-api-mcp/session.jsonSigned in to PeoplePerHour as Maya Reed ([email protected])

You can switch remote debugging off again afterwards. Leave it on if you want the server to pick up a new session by itself after PeoplePerHour signs you out.

connect looks for Chrome's DevToolsActivePort file in the default profile folder. For Chrome Beta, Canary or a custom profile folder, pass --profile-dir "<folder>".

Option B: a Chrome with a debugging port

Chrome does not open a debugging port on your default profile, so start a separate one, sign in to PeoplePerHour there once, and connect to it:

bash
# macOS"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --remote-debugging-port=9222 --user-data-dir="$HOME/.chrome-pph"# Linuxgoogle-chrome --remote-debugging-port=9222 --user-data-dir="$HOME/.chrome-pph"# Windows"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --user-data-dir="%USERPROFILE%\.chrome-pph"
peopleperhour-mcp connect --cdp http://127.0.0.1:9222

--cdp also takes a ws:// DevTools URL, for example of a Chrome on another machine reached over an SSH tunnel.

Option C: paste the cookie by hand

For a server with no Chrome: in Chrome open DevTools on peopleperhour.com, Application > Cookies > https://www.peopleperhour.com, copy the value of api, then:

bash
peopleperhour-mcp connect --token          # paste it, input is hidden# or, without a session file:export PEOPLEPERHOUR_AUTH_TOKEN=...

A pasted token is not refreshed on its own. Paste a new one when PeoplePerHour signs you out.

Check the session at any time:

bash
peopleperhour-mcp status

MCP server

The MCP server lists all 17 tools with their input schemas and a description written for agents. The 13 read tools are marked read-only; --read-only hides the 4 that change your watchlist and saved searches.

Claude Code

bash
claude mcp add peopleperhour -- uvx peopleperhour-api-mcp mcp

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "peopleperhour": {      "command": "uvx",      "args": ["peopleperhour-api-mcp", "mcp"]    }  }}

Cursor

~/.cursor/mcp.json, the same block as Claude Desktop. A ready copy is in mcp.json.

Codex

~/.codex/config.toml:

toml
[mcp_servers.peopleperhour]command = "uvx"args = ["peopleperhour-api-mcp", "mcp"]

Over HTTP

peopleperhour-mcp serve also serves MCP over streamable HTTP at http://127.0.0.1:8787/mcp, for clients that take a URL:

bash
peopleperhour-mcp serveclaude mcp add --transport http peopleperhour http://127.0.0.1:8787/mcp

Then ask your agent things like:

Check PeoplePerHour for web design projects posted since yesterday, skip anything under £200 or with more than 15 proposals, read the briefs of the rest and give me a shortlist of five.

Read the brief of project 4527712, open the files the buyer attached, list what I must deliver and the questions I have to answer, and draft a proposal I can paste.

Is project 4527712 still open, and how many proposals does it have now?

Find logo designers rated 80% or more at £10 to £30 an hour, read the profiles and recent reviews of the top five, and tell me which three to contact.

Save a search for urgent fixed-price design projects called "Urgent design" with a daily email.

REST API

bash
peopleperhour-mcp serve                    # http://127.0.0.1:8787, MCP at /mcp, docs at /docs

Each tool has its own route under /api/v1/peopleperhour, the same paths as the hosted API at cotlet.dev, so code written against one works with the other. Path parts and the query string are arguments.

bash
curl 'http://127.0.0.1:8787/api/v1/peopleperhour/projects/search?query=web%20design&since=2026-10-21T07:00:00Z&limit=20'curl 'http://127.0.0.1:8787/api/v1/peopleperhour/projects/4527712'curl 'http://127.0.0.1:8787/api/v1/peopleperhour/freelancers/search?query=logo%20design&min_rating=80'curl -X PUT 'http://127.0.0.1:8787/api/v1/peopleperhour/projects/4527712/watch'

Any tool by name, body as its arguments:

bash
curl -X POST http://127.0.0.1:8787/api/v1/peopleperhour/tools/search_projects -d '{"category": "design", "limit": 10}'
  • GET /api/v1/peopleperhour/tools: every tool with its route, input schema and an example answer.
  • GET /docs: interactive OpenAPI docs, GET /openapi.json the schema, for n8n, Postman or a generated client.
  • Answers are JSON. List tools return next_cursor; pass it back as cursor for the next page.

The server listens on 127.0.0.1 only. To reach it from another device of yours, set a token, and every request then needs Authorization: Bearer <token>:

bash
PEOPLEPERHOUR_MCP_TOKEN=$(openssl rand -hex 24) peopleperhour-mcp serve --host 0.0.0.0

Python and the example scripts

Straight from Python, no server needed:

python
from peopleperhour_api_mcp import callfrom peopleperhour_api_mcp.scripting import paginate, write_rows
new = list(paginate("search_projects", {"query": "logo", "since": "2026-10-21T00:00:00Z"}, "projects"))write_rows(new, "projects.csv")brief = call("get_project", project_id=new[0]["project_id"])["brief"]

Or one tool from the shell: peopleperhour-mcp call get_project project_id=4527712, or with a JSON object.

Ready scripts in examples/, one per job on the integration page. Each takes --help, and the list scripts take --out file.csv or --out file.json:

ScriptWhat it does
find_new_projects.pyNew projects for one or more keywords in the last N hours, merged, cut on --min-budget (or --hourly-rate) and --max-proposals, then the full brief, questions and files of each one left.
read_project_brief.pyOne project before you write a proposal: brief, attached files, the buyer's questions, proposals, expiry and the 80% price floor.
watch_urgent_projects.pyUrgent projects in a category with fewer than N proposals. --state remembers the last run, for an hourly cron job.
check_project_open.pyWhether projects are still open and how many proposals each has now.
shortlist_freelancers.pyFreelancers for a skill, cut on rate band and rating, with each profile's stats and the average of its latest reviews.
compare_offers.pyThe top Offers for a job side by side: price, delivery days, sales, add-ons and what the seller needs from you.
save_project_alert.pySave a project search with filters and a daily or instant email alert, then list your saved searches.
buyer_daily_digest.pyFor a buyer: your open projects with proposal counts, unread notifications and WorkStreams with unread messages.
median_budgets.pyMedian fixed and hourly budgets per freelancer level for the categories you name, in GBP, USD or EUR.
bash
python examples/find_new_projects.py --query "web design" --query webflow --hours 24 --min-budget 200 --max-proposals 15python examples/read_project_brief.py 4527712python examples/shortlist_freelancers.py "logo design" --hourly-rate 10-30 --min-rating 80python examples/median_budgets.py translation --currency USD

On a schedule, cron on your own computer works while it is on: 0 * * * * cd ~/peopleperhour-api-mcp-server && .venv/bin/python examples/watch_urgent_projects.py --category design --state urgent.json.

Budgets are compared as PeoplePerHour gives them, in the buyer's currency (GBP, EUR or USD), so a floor of 200 means 200 of whatever the buyer picked.

All 17 tools

peopleperhour-mcp tools prints this list, peopleperhour-mcp tools --json adds the input schemas. Times are UTC.

Projects

ToolAccessREST routeWhat it does
search_projectsreadGET /projects/searchOpen projects buyers posted, newest first, with budget, category, proposals and the brief's start.
get_projectreadGET /projects/{project_id}One project's full brief with budget, attachments, interview questions, buyer and proposal count.
list_my_projectsreadGET /projects/mineProjects this account posted as a buyer, with status, budget and proposal count.

Watchlist

ToolAccessREST routeWhat it does
watch_projectwritePUT /projects/{project_id}/watchAdd a project to this account's watchlist (Favourite Jobs) to come back to it later.
unwatch_projectwriteDELETE /projects/{project_id}/watchTake a project off this account's watchlist.
list_watchlistreadGET /projects/watchedOpen projects on this account's watchlist (Favourite Jobs), with budget and proposal count.

Saved searches

ToolAccessREST routeWhat it does
list_saved_searchesreadGET /saved-searchesThis account's saved project searches with their filters and email alert setting.
save_searchwritePOST /saved-searchesSave a project search with an email alert, or rename one or change how often it emails.
delete_saved_searchwriteDELETE /saved-searches/{saved_search_id}Delete one of this account's saved project searches and its email alert.

Freelancers

ToolAccessREST routeWhat it does
search_freelancersreadGET /freelancers/searchFreelancers by skill or keyword, with rate, rating, reviews, completed projects and skills.
get_freelancerreadGET /freelancers/{freelancer_id}A freelancer's public profile: rate, stats, skills, portfolio and the latest reviews on the page.

Offers

ToolAccessREST routeWhat it does
search_offersreadGET /offers/searchFixed-price Offers freelancers sell, by keyword or price, with sales, rating and seller.
get_offerreadGET /offers/{offer_id}One Offer with its full description, what the seller needs from you, prices, add-ons and images.

Account, notifications and WorkStreams

ToolAccessREST routeWhat it does
get_accountreadGET /accountThe signed-in PeoplePerHour account: name, type, buyer stats, unread messages and favourite counts.
list_notificationsreadGET /notificationsThe latest notifications of this account (proposals, messages, project updates) and unread counts.
list_workstreamsreadGET /workstreamsThis account's WorkStreams (conversations with hired freelancers) with the last message.

Categories

ToolAccessREST routeWhat it does
list_categoriesreadGET /categoriesThe 10 project categories with their subcategories and typical budgets per freelancer level.

since makes polling cheap: an agent passes the time of its last check and reads only what arrived after it. One call with since scans at most the 200 newest projects, so a page can hold fewer than limit and still have a next_cursor.

Budgets, rates and prices come as PeoplePerHour gives them: a project in the buyer's currency, freelancer rates, Offers and median budgets in your account currency or the one you pick.

Not in this version: the freelancer side (proposals, your seller profile, your own Offers), posting or editing projects, sending messages in WorkStreams, accepting proposals, and payments, invoices and Proposal credits.

Never built, on purpose: your PeoplePerHour sign-in, email, password and settings, and anything that moves money (Proposal credits, subscriptions, payments). Every request passes a guard that refuses any change to those PeoplePerHour paths.

Configuration

VariableDefaultWhat it does
PEOPLEPERHOUR_MCP_HOME~/.config/peopleperhour-api-mcpFolder of session.json.
PEOPLEPERHOUR_AUTH_TOKENPeoplePerHour api cookie, instead of peopleperhour-mcp connect.
PEOPLEPERHOUR_PROXYProxy for every request to PeoplePerHour, e.g. http://user:pass@host:port.
PEOPLEPERHOUR_MCP_READ_ONLY1 hides and refuses the 4 tools that change PeoplePerHour: watchlist and saved searches (same as --read-only).
PEOPLEPERHOUR_MCP_TOKENBearer token required by serve; needed to listen beyond 127.0.0.1.
PEOPLEPERHOUR_MCP_HOST, PEOPLEPERHOUR_MCP_PORT127.0.0.1, 8787Address of serve.

Security and your PeoplePerHour account

  • Your password never reaches this code. Only cookies are read, and only those of peopleperhour.com.
  • The session file is yours. session.json is created with mode 0600. Anyone who has it can act as you on PeoplePerHour, so keep it out of git and shared folders.
  • Local by default. serve binds to 127.0.0.1 and refuses another address without PEOPLEPERHOUR_MCP_TOKEN.
  • peopleperhour.com only. Requests and redirects outside peopleperhour.com are refused. Attachment links point to PeoplePerHour's file host; the server returns them and does not download them.
  • Your own lists only. 13 tools read. The 4 writes change your watchlist and saved searches and nothing else: no proposal, message or Offer purchase goes to anyone. A watched project lists you among its watchers, so unwatch what you no longer follow.
  • Keep the pace human. A cron job every hour is fine. Hundreds of calls a minute is not how a person browses, and you are responsible for what runs in your account.

Errors

The REST API answers {"error": "<code>", "message": "..."}. The MCP server returns the same code and message as a tool error.

StatusCodeWhat to do
401auth_required, auth_expiredNo session, or PeoplePerHour signed you out. Sign in to PeoplePerHour in Chrome and run peopleperhour-mcp connect.
403target_blockedPeoplePerHour refused the request or showed a bot check. Open peopleperhour.com in Chrome once, then retry.
409captcha_requiredPeoplePerHour asks for a CAPTCHA. Solve it in Chrome.
422invalid_inputAn argument is missing or wrong; the message names it.
429rate_limitedPeoplePerHour is limiting the account. Wait a few minutes.
502target_errorNo such project, freelancer, Offer or saved search, a private or removed one, a filter PeoplePerHour refused (the message gives its reason), or PeoplePerHour answered with an error or changed its site. git pull for the latest tools, or open an issue.

Self-hosted or hosted

This repoCotlet, hosted
Toolsthe same 17the same 17
Runson your computer, while it is onin the cloud, 24/7
PeoplePerHour sessionyour Chrome, cookies in a local fileyour own Cloud Browser in the EU, profile encrypted with AES-256-GCM
When PeoplePerHour changes its sitegit pull once we have fixed itfixed for you, every tool tested daily
Works withMCP clients on your machine, local scriptsClaude.ai and ChatGPT connectors, n8n, Make, Zapier, any HTTP client
Who may use ityou, for noncommercial useteams, businesses, agencies
Pricefreefree 7-day trial with 2,000 credits, no card; then one-time packs from $29 for 5,000 credits

On the hosted version a successful call uses 20 to 30 credits (25 for most tools), failed calls are free, and the Cloud Browser uses 50 credits a day while it has an app enabled for agents. Full pricing.

FAQ

Does PeoplePerHour have an official API? No. PeoplePerHour has no public API, no developer docs and no webhooks (checked 12 Oct 2026). The one built-in alert is Saved Searches: up to 10 searches on the Jobs page, each emailing new results instantly or once a day. PeoplePerHour gives you nothing to call them from code; here save_search and list_saved_searches manage them. Details: cotlet.dev/integrations/peopleperhour-api-mcp-server.

Is there a PeoplePerHour MCP server for Claude, ChatGPT or Cursor? Yes, this one runs on your machine: peopleperhour-mcp mcp for Claude Code, Claude Desktop, Cursor and Codex. ChatGPT and Claude.ai connectors need a public HTTPS URL, which the hosted PeoplePerHour MCP server gives you.

Is this a PeoplePerHour scraper? It returns what people want a job scraper for (new projects with budget, proposals and brief, freelancers and Offers, as JSON or CSV) but runs no headless browser. It calls the same JSON endpoints the PeoplePerHour site calls, in your own account. The one HTML page it reads is a freelancer's profile, for the latest reviews.

Can I get new PeoplePerHour projects as they are posted? Yes. Call search_projects with since set to your last check, from cron or an agent. watch_urgent_projects.py keeps that time in a state file for you.

Can it send proposals or answer buyers? No. Proposals, WorkStream messages, buying Offers, invoices and your Proposal credits are not in this version, and it spends no credits. It can read your WorkStreams and notifications. You write and send proposals and messages on PeoplePerHour yourself.

Can I hire on PeoplePerHour with it? It helps you choose: search_freelancers and get_freelancer for profiles and recent reviews, search_offers and get_offer for fixed-price Offers, list_categories for what buyers usually pay. Posting the project, contacting a freelancer and paying stay on PeoplePerHour.

Do I need a paid PeoplePerHour plan or a freelancer account? No. A free buyer account is enough for all 17 tools.

Does get_project return the project's skills? No, because PeoplePerHour's project data has no list of skills. The skills are in the brief text, which an agent reads.

Why does it need my Chrome? To read your PeoplePerHour session without your password. Chrome is used once per sign-in, not for each call.

What happens when PeoplePerHour signs me out? Calls fail with auth_expired. With Chrome remote debugging on, the server reads the new cookies on the next call (click Allow when Chrome asks); otherwise run peopleperhour-mcp connect again.

Can it run on a VPS or in Docker? Technically yes, with PEOPLEPERHOUR_AUTH_TOKEN. PeoplePerHour then sees your session from a datacenter IP, which looks less like you. For an always-on setup the hosted version keeps your session in your own Cloud Browser on a fixed IP.

Will my PeoplePerHour account get banned? Requests carry Chrome's fingerprint and go out one at a time, and the tools read only what you could open yourself. Nobody can promise a platform never acts. Keep the polling to what a person would do.

Can I use it at work or for my clients? No, the license allows noncommercial use only. For a team, a company or client work, use Cotlet or write to [email protected].

Is it open source? The source is public, the license is not an open source license: noncommercial use only, no business use.

A tool broke or I need another one. Open an issue with the tool name and the error message.

License

PolyForm Noncommercial License 1.0.0. In short:

  • Allowed: noncommercial use: you, for your own personal purposes with your own PeoplePerHour account, or a charity, school, public research or government body. Changing the code, and sharing it under the same license.
  • Not allowed: any commercial use, your own business included; client work; selling or offering it, or a service built on it.

[Cotlet]

Maintained by Cotlet (@cotletdev). PeoplePerHour is a trademark of its owner. This project is unofficial and not affiliated with, endorsed or sponsored by PeoplePerHour.

Source: README.md at commit 3e95c53

Tools

17

get_account

Get account

The signed-in PeoplePerHour account: name, type, buyer stats, unread messages and favourite counts. Returns the account the tools act as: member id, first name and initial, email, account type (buyer or seller), location, currency, profile URL, unread messages, buyer stats (projects posted, listed and completed, freelancers worked with, share of projects awarded, response time) and how many Offers, freelancers and projects it keeps as favourites or watches.

Takes no parameters.

get_freelancer

Get freelancer

A freelancer's public profile: rate, stats, skills, portfolio and the latest reviews on the page. Returns a freelancer's public profile: short name, job title, location, hourly rate, CERT level, rating in percent, review and project counts, skills, languages, full About text, up to 30 portfolio items, and the reviews the profile page shows (usually the latest few, with the project they came from). reviews is the total count; PeoplePerHour does not let older reviews be paged, so only recent_reviews come with text. Times are UTC. Pass a freelancer_id from search_freelancers or an Offer, or the profile URL.

Parametersfreelancer_idrequired

get_offer

Get Offer

One Offer with its full description, what the seller needs from you, prices, add-ons and images. Returns one Offer as its page shows it: title, price in your account currency and in each currency the seller set, delivery days, sales, rating in percent with the count per star, full description, what the buyer must send, add-ons with their price and extra days, image links and the freelancer who sells it. Pass an offer_id from search_offers or the Offer's URL.

Parametersoffer_idrequired

get_project

Get project

One project's full brief with budget, attachments, interview questions, buyer and proposal count. Returns one project as its public page shows it: the buyer's full brief, budget, category, experience level, where it is done, links to the files the buyer attached, the questions the buyer asks in a proposal, how many proposals it has and whether it is still open. client is the buyer's public profile. Times are UTC. Pass a project_id from search_projects or the project's URL.

Parametersproject_idrequired

list_categories

List categories

The 10 project categories with their subcategories and typical budgets per freelancer level. Returns PeoplePerHour's project categories and their subcategories. category is the slug search_projects and save_search take. median_budget is PeoplePerHour's median project budget in the subcategory, fixed price and hourly, by freelancer level (below level 4, level 4, level 5, Top CERT) and on average, in the currency asked for: a guide when pricing a proposal or a project.

Parameterscurrency

list_my_projects

List my projects

Projects this account posted as a buyer, with status, budget and proposal count. Returns the projects the signed-in buyer posted, most recent proposal first, each with its status (open, in_progress, under_moderation, completed and so on), budget, proposal count and the start of the brief. counts is the number of projects per status. Archived projects come back only with status archived. Pass next_cursor back as cursor; it is null on the last page.

Parametersquerycursorstatus

list_notifications

List notifications

The latest notifications of this account (proposals, messages, project updates) and unread counts. Returns the notifications under the bell on PeoplePerHour, newest first: text, link, whether it was read and when it came. unread counts unread notifications, proposals and WorkStream messages. Reading does not mark anything as read.

Takes no parameters.

list_saved_searches

List saved searches

This account's saved project searches with their filters and email alert setting. Returns the project searches the signed-in account saved on the Jobs page: title, email alert (Never, Daily or Instantly) and filters. filters.query and filters.category can go straight into search_projects. PeoplePerHour allows 10 saved searches per account.

Parameterscursor

list_watchlist

List watchlist

Open projects on this account's watchlist (Favourite Jobs), with budget and proposal count. Returns the open projects the signed-in account watches, in the same shape as search_projects. A watched project that has closed drops off the list. Pass next_cursor back as cursor with the same limit; it is null on the last page.

Parameterslimitcursor

list_workstreams

List WorkStreams

This account's WorkStreams (conversations with hired freelancers) with the last message. Returns the WorkStreams of the signed-in account, the conversation PeoplePerHour opens for each hire: title, link, unread message count and the last message with its time. It reads, never sends: replying is done on PeoplePerHour. Pass next_cursor back as cursor; it is null on the last page.

Parameterscursor

search_freelancers

Search freelancers

Freelancers by skill or keyword, with rate, rating, reviews, completed projects and skills. Returns freelancers from the same search as Hire freelancers on PeoplePerHour: short name, profile URL, job title, location, hourly rate in the freelancer's currency, CERT level, rating in percent, review and project counts, skills and the start of their About text. hourly_rate filters in your account currency. get_freelancer returns the full profile. Pass next_cursor back as cursor with the same limit; it is null on the last page.

Parameterssortlimitquerycursormin_ratinghourly_ratetop_certified

search_offers

Search Offers

Fixed-price Offers freelancers sell, by keyword or price, with sales, rating and seller. Returns Offers (fixed-price services, once called Hourlies) from the same search as the Offers page on PeoplePerHour: title, price in your account currency, delivery days, sales, rating in percent, category, tags and the freelancer who sells it. get_offer returns the description, add-ons and images. Pass next_cursor back as cursor with the same limit; it is null on the last page.

Parameterssortlimitquerycursorprice_range

search_projects

Search projects

Open projects buyers posted, newest first, with budget, category, proposals and the brief's start. Returns open projects from the same search as the Jobs page on PeoplePerHour, newest first. Filter by keyword, top category, or posting time: with since, only projects posted after it come back, so an agent polling for new work reads only what arrived since its last check. Times are UTC. budget.type is fixed_price or hourly (then the amount is per hour), in the buyer's currency. freelancer_country is set when only freelancers from that country may send a proposal. get_project returns the full brief. Pass next_cursor back as cursor for the next page; it is null when nothing more matches. With since, one call scans at most 200 of the newest projects, so a page can hold fewer than limit and still have a next_cursor.

Parameterslimitquerysincecursorcategory

unwatch_project

Unwatch project

Take a project off this account's watchlist. Removes the project from the watchlist of the signed-in account. Nobody else is told.

Parametersproject_idrequired

watch_project

Watch project

Add a project to this account's watchlist (Favourite Jobs) to come back to it later. Adds the project to the watchlist of the signed-in account, the heart on the project page. The buyer is not notified. Watching a project already on the list changes nothing. list_watchlist reads the list and unwatch_project takes it off.

Parametersproject_idrequired

Version history

3
  1. v1.0.2LatestOct 25, 2026
  2. v1.0.1Oct 24, 2026
  3. v1.0.0Oct 23, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Cotlet integrations