Support
Help with the MCP integration — connecting it, and what to do when it misbehaves.
The Bimedis MCP integration is built and operated by Bimedis, the company behind the marketplace at bimedis.com. This page covers the integration itself. Questions about an advert, an order or an account belong with marketplace support — same team, wider subject.
1Connecting
One address is all a client needs:
https://mcp.bimedis.com/connect
- ChatGPT — Settings → Apps & Connectors → Developer Mode → Create, paste the URL.
- Claude — Settings → Connectors → Add custom connector, paste the URL, set Authentication to Sign in when needed (the pre-selected No sign-in leaves your account tools unreachable).
- Cursor / VS Code — add an HTTP MCP server with that URL in the client's MCP config.
Catalog search works immediately, with no account. When you first use a tool that touches your own data, the client opens a Bimedis page where you sign in and approve the permissions it asks for. Step-by-step instructions with screenshots are on the main page.
2Common problems
| What you see | What it means |
|---|---|
| The client reports no server, or the tool list is empty | Usually a URL typo, or a client that only accepts SSE-style servers. Check the address
character by character; it must end with /connect and use https. |
| “Connect your Bimedis account to use this tool” | The tool needs an account and the connection is not made yet. Use the client's Connect / Authenticate action; it opens the Bimedis sign-in and consent page. |
| The assistant says a permission is missing | The connection was approved with a narrower set of permissions than the tool needs. Reconnect and approve the set the client asks for — permissions are granted as a whole set. |
| Sign-in fails or the page comes back to the form | Use the same e-mail and password as on the site. A password reset and account recovery are done on the marketplace, not here. |
| Calls start being refused after heavy use | A rate limit. Wait a minute and retry; avoid loops that call the same search repeatedly. |
| Search returns nothing | Try fewer filters and plain keywords — brand and model names work best. If the catalog has the item on the site but the tool does not find it, tell us: that is a bug worth fixing. |
3Managing and revoking access
Every connection is listed in My office → API keys, together with manually created keys. Revoking one connection leaves the others untouched. Revoke a connection whenever you stop using an assistant, or if you suspect its device is compromised.
4Reporting a problem
Write to [email protected] or through bimedis.com/contacts. Please include:
- which assistant and which client version;
- the tool name, if the assistant showed it, and roughly when the call happened (with timezone);
- what you asked for and what came back — the error text verbatim helps most;
- the e-mail of the Bimedis account, if the problem concerns a connected account.
Never send us your access token or your password. Support never asks for either.
5For developers
- llms.txt — the whole server described in plain text.
- server card, protected-resource metadata, authorization-server metadata.
- HTTP API documentation — for integrations that are not MCP.