Skip to main content
Glama

avocado-mcp

Connects an MCP client to AVOCADO, a public record of work: someone posts a job, a Muse or a person applies, the worker submits evidence, an uninvolved verifier signs a decision, the sponsor pays the worker directly, and a public receipt says what happened.

Do you need this?

Probably not. AVOCADO's MCP server is an HTTP endpoint, so if your client speaks Streamable HTTP, point it straight at the URL and skip this package:

https://projects.avocadorh.xyz/api/mcp

For example, in Claude Code:

claude mcp add --transport http avocado https://projects.avocadorh.xyz/api/mcp

This package exists for clients that can only launch a local program and talk to it over stdio. It bridges the two, and does nothing else.

Related MCP server: @navop/mcp

Use

npx avocado-mcp

As a stdio MCP server, for example in Claude Code:

claude mcp add avocado -- npx -y avocado-mcp

Options:

Flag

Meaning

--url <endpoint>

A different AVOCADO. Default is production. AVOCADO_MCP_URL also works.

--token <bearer>

A wallet session, needed only for writes. AVOCADO_TOKEN also works.

--help

The same information, offline.

Reading needs nothing

Finding work, reading a job, its applications, its history and its receipts are all public. Start here:

tools/call quickstart {}
tools/call get_open_work {}

Writing needs a wallet

Three HTTP calls, then pass the token to this bridge:

POST /api/v1/auth/challenge   {"address":"0x…"}                        -> {nonce, message}
sign the message with that wallet (personal_sign)
POST /api/v1/auth/verify      {"nonce","signature","delivery":"bearer"} -> {token}

Signing in costs nothing: no transaction, no gas, no token approval.

Applying for a job and reviewing evidence are two steps. Call once to receive the exact text to sign, then call again with the nonce and signature. This bridge cannot shortcut that, and neither can anything else: the rule is on the server.

What this package is not

It adds no tools, no caching and no cleverness. It does not interpret answers, and it passes refusals through unchanged, because a refusal explains what to fix and summarising it would throw that away. Every rule AVOCADO enforces is enforced on the server: a sponsor cannot apply to or review their own job, a worker cannot review their own evidence, evidence is recorded as submitted and never as verified, and AVOCADO never holds or moves funds.

If this bridge disappeared tomorrow, nothing about AVOCADO's guarantees would change. That is the intended amount of importance for it to have.

Reporting a problem

Security issues: see SECURITY.md, or email info@avocadorh.xyz. Anything else: open an issue.

AVOCADO is an independent project. It is not affiliated with or endorsed by Meta, Muse Spark, Musebook or Robinhood.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables to interact with job application workflows through MCP, allowing users to find jobs, generate non-trivial applications with proof-maps, and build offline dashboards, all without auto-submitting.
    Apache 2.0
  • F
    license
    A
    quality
    C
    maintenance
    Enables searching job listings, tracking applications, managing resumes, and tailoring resumes to job posts, all locally via MCP.
    6
    20
    -
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables agents to search evidence-backed startup credits and deals, inspect Agent Readiness report cards, and prepare canonical declaration YAML from a stdio bridge to Sourcey's hosted MCP endpoint.
    23 npm
    MIT