Jiji MCP

An independent, MIT-licensed MCP for Jiji, with no browser extension required. Sign in directly on Jiji in the companion's dedicated Chrome window. Codex, Claude, ChatGPT and Grokbot can share your companion through local MCP or an authenticated HTTPS relay.

This project is not affiliated with Jiji. Undocumented endpoints and page selectors can change. Version 0.3 adds a platform catalog with 73 read resources, 35 locally approved changes and 42 browser workflows. Coverage includes direct tools and owner handoffs; opening a workflow does not automate its final steps. Not every endpoint or write has been live-tested. See FEATURES.md and VALIDATION.md.

Capabilities

There are 21 MCP tools. There is no MCP send/approve tool. jiji_prepare_message returns a local approval page showing the exact seller, listing and message. Only the owner can submit that page. Each plan expires after ten minutes and can be used once. An uncertain result is not retried automatically. Payments, media uploads, identity verification and credential changes are completed directly on Jiji through owner workflows. Account changes use the same local approval boundary.

Related MCP server: glongus-mcp

Native category filters

For used/new, brand or type filters, first call jiji_account_data with resource: "listing_filters" and the category slug. Use the returned exact filter_name and values; attribute identifiers vary by category. Supply that category as category_slug when searching. Unscoped attribute filters are rejected because Jiji can silently ignore them.

For example, the verified solar-panel category supports:

{
  "query": "450w solar panel",
  "category_slug": "solar-energy-products",
  "filters": {
    "filter_attr_1484_condition": "Used",
    "filter_attr_1483_type": "Solar Panels"
  },
  "limit": 8
}

Both jiji_search and jiji_market_prices accept category/region slugs, prices and these native filters. Values can be a string or an array for multiple selections. Pagination serves any remaining same-page results first, then follows Jiji’s returned next-page URL, retaining filters. A small limit no longer hides results from the final page. Market prices remain a one-page asking-price sample; query words such as “used” alone are not condition filters. Clients may need a tool refresh to discover the added optional inputs.

Install (macOS)

Requires Node.js 22+ and Google Chrome.

git clone https://github.com/atomicman57/jiji-mcp.git
cd jiji-mcp
npm ci
npm run install:companion
npm run companion

Open http://127.0.0.1:38473, choose Open Jiji sign-in, and log in directly on Jiji in the companion's Chrome window. Passwords, verification codes and cookies are never accepted by MCP tools or exported from the browser. The profile lives in a private application-data directory outside the repository. Complete any Jiji challenge manually; there is no bypass or automatic restriction retry.

The companion is a local service; keep it running during use. A browser extension, native-messaging host and exported cookie file are not needed.

Local agents

Use the absolute paths printed by install:companion:

{
  "mcpServers": {
    "jiji": {
      "command": "/absolute/path/to/node",
      "args": ["/absolute/path/to/jiji-mcp/src/server.mjs"]
    }
  }
}

For Codex:

[mcp_servers.jiji]
command = "/absolute/path/to/node"
args = ["/absolute/path/to/jiji-mcp/src/server.mjs"]

The stdio server talks to the companion through a mode-0600 Unix socket inside a mode-0700 directory. Multiple agents can share one companion. Reload MCP discovery or restart the client after updates.

ChatGPT, Claude and Grokbot over HTTPS

Enable the cloud relay in the application-data config.json printed by the installer. Set cloudEnabled: true, cloudOrigin to a trusted HTTPS server origin, and credentialHelper to an executable compatible with the encrypted credential-helper interface below. Restart the companion.

1. Add the hosted /mcp URL as a custom MCP app/connector in your agent, using OAuth.

2. On the companion control page choose Generate pairing code.

3. Enter that one-time code on the MCP server's connection page and approve the displayed access. To use the account catalog, explicitly enable the separate account-features checkbox. Older grants retain their earlier access until reconnected.

4. Follow Continue to your agent. Repeat with a fresh code for each agent.

OAuth connects an agent to your companion; Jiji sign-in happens only in the dedicated Jiji browser. Each companion/server origin has a separate random 256-bit identity. Pairing codes expire in ten minutes and are consumed once. The relay isolates users and stores no Jiji passwords or cookies. A cloud agent cannot approve a message or account change through an MCP call. Expanded private account access is recorded in the OAuth grant; a client cannot enable it with a request header.

The optional credential-helper CLI reads/writes a document named jiji-mcp-companion in an encrypted store. It must support list-documents --prefix NAME and get-document NAME with JSON on stdout, plus put-document NAME with JSON on stdin. The document contains an identities object keyed by HTTPS origin. The application pipes these values internally and never logs them. Local MCP tools do not need a credential helper or cloud identity.

Self-host the relay

npx wrangler login
npx wrangler d1 create jiji-browser-mcp-storage

Copy wrangler.jsonc to wrangler.local.jsonc, replace its D1 database ID and initialize it with npx wrangler d1 execute MCP_STORAGE --remote --config wrangler.local.jsonc --file cloud/d1-schema.sql, then run:

npx wrangler deploy --config wrangler.local.jsonc --durable-objects-code-update-mode immediate

The Worker uses Cloudflare D1 and per-user Durable Objects, plus @cloudflare/workers-oauth-provider. Configure PUBLIC_ORIGIN for a custom domain. Companions use hibernating WebSockets; hosting usage costs and limits apply to the operator. Never commit credentials, browser profiles or personal deployment configuration.

Development and tests

npm run cloud:build
npm test
npm audit

Tests cover catalog schemas, credential/payment-field rejection, per-user OAuth routing, expanded-access consent, request/approval ID separation, the local HTTP/Unix-socket boundary, and one-time approval state. Live sign-in and each client connection must be verified separately. The tests never contact a real seller or initiate payment.

See SECURITY.md for trust boundaries and FEATURES.md for explicit coverage and gaps.

Idle cloud transport

The companion uses an authenticated WebSocket to /bridge/socket. The relay accepts it through the Durable Object Hibernation API, and native protocol ping/pong keeps the connection healthy without an application heartbeat. Idle polling is retired: /bridge/poll returns HTTP 426 so an old companion cannot silently consume continuous runtime. Update the companion and restart its local service when deploying this relay version. Existing OAuth grants and browser sign-in are retained. Reconnect never replays an uncertain operation. Search pagination is saved in the existing Durable Object storage so it survives hibernation. No new cron, KV namespace, database, or paid plan is required.

ChatGPT compatibility

On 2026-10-27, the web verification chat rendered Jiji tool results correctly with GPT-5.6 Sol Medium. GPT-6 returned successful connector calls but its final response displayed “This response couldn’t load.” If affected, select GPT-5.6 Sol in that Jiji chat and send a fresh request. This is an observed client workaround; it does not establish that every model has the issue. Tool results include both JSON text and a matching structuredContent.data payload with an output schema.