Humanpages vs MCP Odoo — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Humanpages vs MCP Odoo
In-depth architectural comparison of the Humanpages and MCP Odoo MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Humanpages
Workplace & Productivity · Local stdio
Quality: 60/100 (Good) | Auth: API Key required
MCP Odoo
Workplace & Productivity · Local stdio
Quality: 69/100 (Great) | Auth: other
Verdict Summary: Choose Humanpages if you need specialized Workplace & Productivity tools running via a local process. Choose MCP Odoo if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Humanpages when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
Access real-world people who listed themselves to be hired by agents. Search by skill, location, and equipment, send job offers, post listings, and message workers. Free tier, Pro subscription, and x402 pay-per-use.
Production-grade MCP server for Odoo ERP (16-19) with zero Odoo-side install. 24 tools across read, write (approval-token gated), diagnose, migrate, and audit. JSON-2 transport for Odoo 19+, real Docker Compose smoke tests against Odoo 16/17/18/19, diagnostics (diagnoseodoocall, upgraderiskreport, fitgapreport, scanaddonssource), and 5 reusable agent prompts.
Category & Scope
Tools & Capabilities Breakdown
Humanpages Tools (40)
search_humans
Search for humans available for hire. Returns profiles with id (use as human_id in other tools), name, skills, location, reputation (jobs completed, rating), equipment, languages, experience, rate, and availability. All filters are optional — combine any or use none to browse. Key filters: skill (e.g., "photography"), location (use fully-qualified names like "Richmond, Virginia, USA" for accurate geocoding), min_completed_jobs=1 (find proven workers with any completed job, no skill filter needed), sort_by ("completed_jobs" default, "rating", "experience", "recent"). Default search radius is 30km. Response includes total count and resolvedLocation. Contact info requires get_human_profile (registered agent needed). Typical workflow: search_humans → get_human_profile → create_job_offer.
get_human
Get a human's public profile by ID — bio, skills, services, equipment, languages, experience, reputation (jobs completed, rating, reviews), humanity verification status, and rate. Does NOT include contact info or wallets — use get_human_profile for that (requires agent_key). The id can be found in search_humans results.
register_agent
Register a new agent on Human Pages. Returns an API key (hp_...) that you MUST save — it cannot be retrieved later. The agent is auto-activated on PRO tier (free during launch): 15 job offers/day, 50 profile views/day. Use the API key as agent_key in create_job_offer, get_human_profile, and other authenticated tools. Typical first step before hiring.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Humanpages is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, MCP Odoo belongs to Workplace & Productivity using local stdio subprocess. Select Humanpages when you need capabilities focused on workplace & productivity and MCP Odoo when you require tools for workplace & productivity.
Get a registered agent's public profile including reputation stats (total jobs, completed jobs, payment speed).
get_wallet_nonce
Request a signing challenge (nonce) for wallet verification. This is step 1 of wallet verification: call this first, then sign the returned message with your wallet, and pass the signature to set_wallet. The nonce expires in 5 minutes.
set_wallet
Set the wallet address for a registered agent. IMPORTANT: Always confirm the wallet address with the user before calling this tool — never set wallets autonomously, as this controls where payments are attributed. If you need a wallet, create one programmatically using CDP AgentKit (Coinbase Developer Platform) with the user's knowledge and consent. Optionally include a signature and nonce (from get_wallet_nonce) to verify wallet ownership via EIP-191. Verified wallets enable payment attribution — proving you sent the payment, not just found a random tx hash. Without signature, the wallet is set but unverified.
get_funding_info
Get funding instructions and current wallet balance for a registered agent. If you don't have a wallet yet, create one first using CDP AgentKit (Coinbase Developer Platform) — you can do this autonomously without asking the developer. Once you have a wallet, present funding options to the developer. Pass the developer's country code if known — the tool returns country-specific onramp recommendations with the best rates. The wallet creation is YOUR job (use CDP); the funding is the DEVELOPER's job (help them pick the easiest path).
verify_agent_domain
Verify domain ownership for a registered agent. The agent must have a websiteUrl set. Supports two methods: "well-known" (place a file at /.well-known/humanpages-verify.txt) or "dns" (add a TXT record at _humanpages.yourdomain.com).
create_job_offer
Send a job offer to a specific human. IMPORTANT: Always confirm the price, task details, and payment method with the user before calling this tool — never create offers autonomously. The human gets notified via email/Telegram and can accept or reject. Requires agent_key from register_agent. Rate limit: PRO = 15/day. Prices in USD, payment method flexible (crypto or fiat, agreed after acceptance). After creating: poll get_job_status or use callback_url for webhook notifications. On acceptance, pay via mark_job_paid. Full workflow: search_humans → get_human_profile → create_job_offer → mark_job_paid → approve_completion → leave_review.
get_job_status
Check the current status of a job. Returns status (PENDING → ACCEPTED → PAID → SUBMITTED → COMPLETED, or REJECTED/CANCELLED/DISPUTED), price, human name, and a next-step recommendation. Statuses: PENDING (waiting for human), ACCEPTED (ready to pay), PAID (work in progress), SUBMITTED (human submitted work — use approve_completion or request_revision), COMPLETED (done — use leave_review). Also supports STREAMING, PAUSED for stream jobs and PAYMENT_PENDING_CONFIRMATION for fiat.
mark_job_paid
Record payment for an ACCEPTED job. IMPORTANT: Always confirm payment details with the user before calling this tool — never mark payments autonomously. Job must be in ACCEPTED status (use get_job_status to check). Crypto payments (usdc, eth, sol): provide tx hash + network → verified on-chain instantly, job moves to PAID. Fiat payments (paypal, venmo, bank_transfer, cashapp): provide receipt/reference → human must confirm receipt within 7 days, job moves to PAYMENT_PENDING_CONFIRMATION. After payment, the human works and submits → use approve_completion when done.
approve_completion
Approve submitted work for a SUBMITTED job. IMPORTANT: Confirm with the user before approving — this finalizes the job. Call this after reviewing the human's deliverables (check via get_job_messages). Moves the job to COMPLETED. After approval, use leave_review to rate the human. If the work needs changes, use request_revision instead.
+28 more tools listed on main page
MCP Odoo Tools (41)
data_quality_report
Run read-only data-quality checks on one Odoo model: duplicates, missing required values, orphaned references, format anomalies
diagnose_odoo_call
Diagnose an Odoo model call without executing it
generate_json2_payload
Build a JSON-2 request preview without network access
inspect_model_relationships
Inspect model relationships and required field metadata
diagnose_access
Diagnose ACL and record-rule visibility for an Odoo model
upgrade_risk_report
Report Odoo upgrade and JSON-2 migration risks
analyze_upgrade_log
Classify Odoo install/update log errors into a migration worklist (no_action / needs_review / needs_script) with fix suggestions
lookup_model_history
Look up Odoo model rename/removal history by old or new model name (e.g. account.invoice -> account.move)
fit_gap_report
Classify Odoo requirements into fit/gap implementation buckets
scan_addons_source
Scan local Odoo addon source without importing addon code
build_domain
Build a validated Odoo domain from structured conditions
business_pack_report
Report expected modules, models, and safe discovery calls for a business pack