MCP server
For AI assistants (Claude, ChatGPT) — a different interface, the same rules.
Besides api.ajungem.ro/v1, Ajungem.ro also has an MCP server, for AI assistants: https://ajungem.ro/mcp (with an account, OAuth 2.1 with PKCE) and https://ajungem.ro/mcp/public (no account).
How it differs from the API
API (api.ajungem.ro/v1) | MCP (/mcp) | |
|---|---|---|
| Public | Read routes | Public tools (search, estimate, a single listing) |
| With an account | API keys, read-only | OAuth, create_listing, cancel_listing, publish_vehicle, my_listings, my_vehicles, list_offers |
| Writing | Planned | create_listing, cancel_listing, publish_vehicle — already live |
| Sending or accepting offers | Never through API/MCP | Never through API/MCP |
| Phone numbers | Never | Never |
MCP already has write tools (publish a listing, publish a free vehicle) that the REST API doesn't have yet in batch 1 — they're built on the same server functions (createListing, createVehicleOffer), with the same caps as the site.
list_offers reads the offers received on your own listings — the same data as GET /listings/{ref}/offers in the API, but through the MCP protocol.
How to connect it
See the presentation page ajungem.ro/mcp for the exact steps, in Claude, ChatGPT, or Cursor. Authorization is OAuth 2.1 with PKCE; the only permissions are listings:read (always) and listings:write.
api.ajungem.ro/v1 and /mcp are separate OAuth resources (RFC 8707): a token issued for MCP doesn't work on the REST routes, and the other way around.