Skip to content
Bimedis

Live Model Context Protocol · Streamable HTTP · 17 tools

The medical equipment marketplace, inside your assistant

Bimedis lists hundreds of thousands of used, refurbished and new medical devices and spare parts. Point ChatGPT, Claude, Cursor or VS Code at one URL and it reads the live catalog — no account, no code. Add your personal key and it also runs your shop: adverts and buyer chats.

https://mcp.bimedis.com/connect

Free, unauthenticated catalog search. Account tools open after a one-click sign-in: you see what the assistant asks for, approve it once, and revoke it whenever you like.

17tools in one endpoint
5work without any key
$0to use, for everyone
2 minto connect a client

What it does

Two jobs, one endpoint

The same URL serves everyone. What the assistant may do depends only on whether you handed it a key.

Search the catalog

Filter by category, producer, model, price, condition, year, stock state and the country a listing ships from, then pull the full listing — description, photos, condition, year, where it ships from. Deep-research clients get the standard search and fetch pair.

No sign-in

Run your shop

List, read, create, update and delete your own adverts; read your conversations as seller or buyer, reply in them, open a thread with a seller from any listing, and check what is still unread.

Your account

Tool catalog

Seventeen tools your assistant can call

Every tool is described to the model, so you never type a tool name yourself — you ask in your own words and the assistant picks. Here is the full surface, with nothing hidden.

Catalog

no key

Open to any client, authenticated or not. Seller phone numbers, e-mails and messenger handles are stripped from every public result.

search_listings

Search live adverts by free text plus filters: equipment or spare parts, category, producer, model, price range, condition, year of manufacture, country it ships from and stock state — sorted by relevance or cheapest first. Returns page after page of compact results.

get_listing

Full detail of one advert: the seller’s full description, price and currency, condition, year, stock, warranty, photos, where it ships from and to.

search

The OpenAI deep-research shape of the same search: id, title, url. Used automatically by ChatGPT research runs.

fetch

The deep-research companion: full text of one result by the id that search returned.

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. Command-line clients use a personal MCP key instead.

no key works for anyoneneeds your key acts inside your accountwrites changes something — clients ask before running these

How to connect

Two minutes, any MCP client

Add the endpoint — that is the whole setup. When the assistant first reaches for your account, Bimedis asks you to sign in and approve; only command-line clients that cannot open a browser still carry a personal key in an Authorization header.

One click, no key to copy

ChatGPT and Claude ask Bimedis for access themselves: a Bimedis page opens, lists what the assistant wants to reach — your adverts, your conversations — and you press Sign in and allow. Access is all or nothing, so there is nothing to tick.

The connection belongs to that one assistant: it appears in My office → API keys and revoking it leaves your other assistants and your own integrations running. The client never receives your password, and no key passes through your clipboard.

GPT

ChatGPT

  1. Settings → Apps & Connectors → Advanced settings → turn on Developer mode (Plus, Pro, Business, Enterprise, Edu).
  2. Apps & Connectors → Create.
  3. Name it Bimedis, paste the URL, authentication None.
  4. Mention Bimedis in a chat, or pick it as a Deep Research source.
  5. The first time you ask about your own adverts or chats, ChatGPT opens the Bimedis sign-in page — approve it once.
# URL — the only thing you paste
https://mcp.bimedis.com/connect
C

Claude — web & desktop

  1. Settings → Connectors → Add custom connector.
  2. Name it Bimedis and paste the URL.
  3. Under Authentication pick Sign in when needed — Claude pre-selects No sign-in because search works without an account, and then it never offers to connect your adverts and chats. Leave OAuth client on the recommended default. Add it.
  4. Turn the connector on in a chat from the tools menu.
  5. The first time it touches your account, Claude opens the Bimedis sign-in page — approve it once.
# URL — the only thing you paste
https://mcp.bimedis.com/connect
>_

Cursor, VS Code, Windsurf

Use the one-click buttons at the top of this page, or write the server into the client's MCP config by hand. The URL is the whole config — these clients speak OAuth, so the first time the assistant reaches for your account they open the Bimedis sign-in page themselves.
{
  "mcpServers": {
    "bimedis": {
      "url": "https://mcp.bimedis.com/connect"
    }
  }
}
$

Claude Code & other CLIs

One command for Claude Code — no key in it. Run /mcp afterwards and pick bimedis to sign in; the browser opens the Bimedis page and the client keeps the connection itself. Any client with the Streamable HTTP transport works the same way: GitHub Copilot, Gemini CLI, LibreChat. Only your own SDK code needs a personal key in the Authorization header.
claude mcp add --transport http bimedis \
  https://mcp.bimedis.com/connect

Command-line clients

If your client cannot open a browser

Everything above happens without a key. This page is only for terminals, scripts and your own code — anything that cannot open a sign-in page. The key identifies you, so the assistant acts as you under the same rules as the website, and nothing more: outside adverts and conversations it is rejected.

1

Sign in on bimedis.com

Use the account that owns the adverts and conversations you want the assistant to work with.

2

My office → API keys

Open bimedis.com/my-office/api-keys and find the “AI assistant keys (MCP)” block. The page is open to every signed-in account, on desktop and on the phone.

3

Create an MCP key

Name it after the assistant (“Claude”, “ChatGPT”). The key looks like 12345|abcdef… and is shown once. Keep one key per assistant.

4

Give it to your client

Always as the header Authorization: Bearer YOUR_KEY. The key is never put in the address: anything in a URL ends up in browser history and proxy logs.

Treat it as a password

Anyone holding the key acts as you inside that scope. Keep it in the header, never in the URL — a URL ends up in browser history and proxy logs — and revoke it the moment it leaks.

Revoking takes one click

Press “Revoke” next to the key in the list. Only that key stops working; your other assistants and integrations keep running.

Do not confuse it with a personal API key

The same page also has “Personal API keys” (“Create API key”, for accounts with auto-posting): those are full-access REST keys for CRM and your own integrations, not limited to the assistant tools. For assistants always use “Create MCP key” — each key can be revoked on its own without touching the others.

Fair-use limits

About 120 tool calls a minute per account and 180 per client IP. Ordinary use stays far below that; if you hit a limit the tool says so and the assistant retries.

FAQ

Questions people actually ask

What is MCP, in one sentence?

The Model Context Protocol is an open standard that lets an AI assistant call outside services. Bimedis runs one, so instead of describing listings from memory, your assistant reads the live marketplace.

Do I need an account or a key?

Not for searching — catalog search and listing details are open to everyone. The twelve tools that touch your own adverts and conversations need your account: in ChatGPT or Claude you simply sign in when they ask, and only command-line clients still want a personal MCP key.

How does signing in work?

The assistant opens a Bimedis page listing what it wants to reach. You sign in there with your e-mail or with Google — the page belongs to Bimedis, the assistant never sees your password — and press “Sign in and allow”. Access is all or nothing, and the connection shows up in My office → API keys, where one click revokes it without touching anything else.

What exactly can an assistant do with my account?

List, read, create, update and remove your adverts; read your conversations as seller or buyer and reply in them; start a thread with a seller; read your unread counter. It cannot see your password, change account settings or touch payments.

Does reading a conversation mark it as read?

Yes — the same as opening that chat in your Bimedis office. If you want the unread badge to stay, ask for the unread count instead of opening the thread.

Will my message go to other sellers?

No. Starting a conversation from a listing sends it to that seller only. The website's “share with similar sellers” option is never used by the assistant.

Are seller contacts exposed in search results?

No. Phone numbers, e-mail addresses and messenger handles are stripped from public results, even when a seller typed them into a description. Contact happens through a normal Bimedis conversation.

Which clients work?

Any MCP client with the Streamable HTTP transport: ChatGPT in developer mode, Claude on the web and desktop, Claude Code, Cursor, VS Code with GitHub Copilot, Gemini CLI, Windsurf, LibreChat and others.

Are there rate limits?

Yes: roughly 120 tool calls a minute for one account and 180 for one client IP, plus a service-wide ceiling. Ordinary use stays far below that; if you do hit a limit, the tool says so and the assistant can retry a minute later.

In which language does it answer?

The server works in English. Your assistant can translate results into whatever language you chat in.

Something looks wrong — where do I report it?

Write to [email protected] with the tool name and what you asked for. The full HTTP API is documented at apis.bimedis.com.