jameda MCP server: let your AI agent search doctors and read free slots
Wield is an MCP server that gives your AI agent two jameda tools. jameda.de/search-doctors finds doctors and practices by specialty and city, with ratings and whether online booking has free slots. jameda.de/get-slots reads the free appointment slots of one doctor over 7 days. Both run from a tab in your own browser, and neither needs a login.
jameda Get free online appointment slots for a doctor on jameda
Read-only, no loginRuns in your browser only
Parameters (5)
| Metric | Wield recipe | Browser Use + Claude Sonnet 5.5 |
|---|---|---|
| Success | 100% | 100% |
| Median time | 211 ms | 46 s |
| Cost per run | $0 | $0.128 |
9 runs each, 7 November 2026. How we measure
What your agent gets
| Recipe | What it does | Login | Status (7 Nov 2026) |
|---|---|---|---|
jameda.de/search-doctors | Doctors and practices by specialty and city, with address, rating, review count and booking status | No | OK, 5 of 5 checks |
jameda.de/get-slots | Free online slots for one doctor and address over 7 days, grouped by day, plus the next free slot | No | OK, 3 of 3 checks |
search-doctors returns the ids that get-slots needs: the doctor id and the address id. The practice must have online booking. Each slot in the result carries a booking link. Paid "Anzeige" placements are dropped by default.
In a check on 7 November 2026, get-slots returned 4 slots over 7 days, plus the next free slot.
How a request flows
- You ask your agent: "Find a general practitioner in Hamburg with online booking and a free slot this week."
- The agent calls
find_recipe, thenrunwithjameda.de/search-doctorsand the specialty and city. wield-mcppasses the run through the local bridge to the Wield extension.- For each practice it picks, the agent runs
jameda.de/get-slots. The extension sends the requests from a jameda.de tab, so they carry your normal browser session. - The results go back to your agent. Nothing passes through wield.run.
What leaves your computer
The only host is www.jameda.de. Each search page is one request, and the slot lookup is one request. The recipes read public pages, and they never sign in or act for you.
Health searches are sensitive, so results stay on your device. They never appear in telemetry, which is off by default. Wield logs each request locally with method, host, path, status and timing, and never logs bodies or query values. Wield never reads, copies or sends your cookies or passwords.
jameda terms, in plain words
We have not reviewed jameda's terms as a lawyer would, so this is not legal advice. Our reading is that jameda's terms forbid automated retrieval of profile data. Both recipes run one search page at a time, that you start, from your own browser. They are not for polling slots in a loop or collecting profiles in bulk. Check jameda's terms yourself before you automate anything else.
Limits and what is not working yet
- Read only. The recipes find doctors and slots. They do not book. You finish the booking on jameda with the booking link.
- Online booking only.
get-slotsworks only for doctors whoseonline_bookingis true. - Fixed time offset. The slot times use a fixed offset of +01:00. During summer time the offset is off by one hour, so check the time against the booking link.
- Run limits apply. A run has at most 12 steps, 40 requests, 5 MB per response and 60 seconds.
FAQ
Is there an official jameda MCP server?
Not that we know of as of 7 November 2026.
Which AI apps work with it?
Any MCP client. npx -y wield-mcp init sets up Claude Desktop, Claude Code, Cursor and Codex. Other MCP clients work with the standard stdio config.
Does it need a jameda login?
No. Both tools work without an account.
How fast is it compared with a browser agent?
Both sides passed every run here, so the difference is speed and cost. As of 7 November 2026, and still preliminary, the Wield recipe for free slots passed 9 of 9 runs with a median of 211 ms. Browser Use with Claude Sonnet 5.5 passed 9 of 9, with a median of 46.0 seconds and $0.13 per run. For doctor search, the Wield recipe had a median of 447 ms against 51.2 seconds for the browser agent, at $0.15 per run. See the jameda slots benchmark.