# Bimedis MCP Server

> Remote Model Context Protocol server for Bimedis, the global B2B marketplace for used,
> refurbished and new medical equipment and spare parts. One HTTPS endpoint exposes 17 tools:
> catalog search works with no account at all, while adverts and buyer conversations
> work under the user's own account: the client sends the user to a
> Bimedis consent page once, and the access it gets is limited to the permissions approved there.

- Endpoint: https://mcp.bimedis.com/connect
- Transport: Streamable HTTP (stateless), MCP specification
- Auth: none for catalog tools; OAuth 2.1 (authorization code + PKCE S256) for account tools
- Authorization server metadata: https://mcp.bimedis.com/.well-known/oauth-authorization-server
- Protected resource metadata: https://mcp.bimedis.com/.well-known/oauth-protected-resource/connect
- Consent screen: https://mcp.bimedis.com/auth — the user signs in with e-mail or Google and approves in one click
- Fallback for clients that cannot open a browser: `Authorization: Bearer <MCP key>`, issued by the user at
  https://bimedis.com/my-office/api-keys — "AI assistant keys (MCP)". The same page lists and revokes connections.
- Price: free
- Language: English
- Rate limits: ~120 tool calls/minute per account, ~180/minute per client IP

## Tools without a key (5)

- search_listings: search live adverts by text, category, producer, model, price range, condition, year of manufacture, country it ships from, stock state and type (equipment or spare parts)
- get_listing: full detail of one advert
- search: OpenAI deep-research search shape (id, title, url)
- fetch: OpenAI deep-research fetch of one result by id
- connect_account: tells you where to start the Bimedis sign-in in your AI client (Connect / Authenticate); the account itself is connected through the client's standard OAuth sign-in

## Tools under the user's account — adverts and conversations (12)

- get_my_profile: name and e-mail of the connected account
- list_my_adverts, get_my_advert: read your own adverts
- create_advert, update_advert, delete_advert: publish, change and remove your adverts
- list_advert_options: reference values a valid advert needs (categories, currencies, conditions, stocks, countries)
- list_conversations, get_conversation: read your threads as seller or buyer (reading marks them read)
- send_message: reply in an existing thread
- contact_seller: start a thread with the seller of a listing
- get_unread_count: unread messages waiting

## Permissions asked on the consent screen

- profile:read — account name and e-mail
- adverts:read / adverts:write — read your adverts; publish, edit and delete them
- messages:read / messages:send — read your conversations; reply and start new ones

Approval is all or nothing: the user either grants the whole set the client asked for, or nothing.

## Boundaries

- Public catalog results never carry seller phone numbers, e-mail addresses or messenger handles.
- Neither a connection nor a key can read the password, change account settings or touch payments.
- A connection is limited to the permissions approved on the consent page; a call outside them is refused.
- Each connection and each key is revocable on its own; a user may hold several, one per assistant.

## Links

- Landing and setup guide: https://mcp.bimedis.com/
- HTTP API documentation: https://apis.bimedis.com/api/v2/documentation
- Marketplace: https://bimedis.com/
- Integration support: https://mcp.bimedis.com/support (support@bimedis.com)
- Marketplace support: https://bimedis.com/contacts
- MCP usage terms: https://mcp.bimedis.com/terms (supplements https://bimedis.com/agreements.html)
- MCP data practices: https://mcp.bimedis.com/privacy (supplements https://bimedis.com/cookies.html)