ipa-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IPA_LIBRARY | No | Path to the synced copy of the site's library folder (e.g. the 'biochem-ipa - Documents' folder created by OneDrive). The server finds the synced folder by itself (OneDrive's registry on Windows, the usual places on macOS); set this only if it does not. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ipa_statusA | Is the synced library here, how fresh is it, and who is the user? Call first when anything fails; it gives the setup steps when the library is missing. |
| ipa_set_userA | Remember who the user is (name, lab - Aumeier, Dudin, Kaksonen, Kruse, Roux or other) and, if auto-detection failed, where their synced library is. Ask the user once, then call this. |
| ipa_equipmentA | Every item on the site - microscopes (kind 'scope'), hoods, VM desktops - with id, lab, aliases, room, page, objectives, light paths and laser lines. Filter by lab and/or kind. |
| ipa_findA | Which item does the user mean? 'the spinning disc', 'the Nikon scope', 'Dobby'... Ranked candidates; the user's lab (from ipa_status) breaks ties. If several labs have a match, ask the user which lab rather than guessing. |
| ipa_itemA | Everything the site knows about one item, structured: identity, objectives (with immersion and NA parsed from the tag), light paths, laser lines, the page's outline, where to book it, and which measurements exist (PSF per objective, laser power per line). Read a page section with ipa_page for the prose. |
| ipa_pageB | Read a page of the site (Markdown): by id ('dudin_scope_sdc-nikon', 'lab-vms', 'protocol-psf', 'image-analysis') and optionally one section by title ('Software', 'Known quirks', 'What is installed'). A long page without a section gives its outline and the first part; ask for sections to read the rest. Cite the page's URL in answers. |
| ipa_searchA | Search every page and the measurement READMEs (regular expression, case-insensitive). Each hit: page, nearest heading, line. Good for 'is napari installed', 'TeamViewer', 'correction collar', a filter name, a software version. |
| ipa_laser_powerA | Laser power at the sample, per scope, laser line and light path: every measurement by date with the change since the first and since the previous one (per cent). Scope is an id from ipa_find. With nothing measured for the scope, says so and gives the protocol and whom to ask. The protocol compares runs within one light path only. |
| ipa_psfB | PSF measurements: per session (scope, objective tag such as '100x-146-oil', light path, date), the FWHM in x, y, z per channel against the expected value, the chromatic shift, and the local path of each channel's PSF image (psf_.tif, for deconvolution). Newest first. With nothing measured, says so and gives the protocol and whom to ask. |
| ipa_buildsC | The courses, presentations and viewers on the site (interactive HTML in the library), with title, summary, URL and source repository. kind: course | presentation | viewer. |
| ipa_bookingC | Where to book an item: its page (the calendar is embedded there), the SharePoint list behind it, and the booking directory of the whole site. Booking is per lab: confirm the user's lab (ipa_status) before opening another lab's scope. |
| ipa_openB | Open a page of the site, a booking list or a library file in the user's browser. Only URLs of the site are accepted. |
| ipa_filesA | List the files of a library folder - 'data/equipment/', 'data/psf//raw', 'data/laser-power' - with size, URL and whether OneDrive has downloaded each one. Raw acquisitions are large: list before reading, and read only what is needed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a clearly distinct resource or action: setup/status, inventory listing, item resolution, item detail, page reading, global search, laser-power measurements, PSF measurements, builds, booking pointers, opening URLs, and file listing. The only minor overlap is that ipa_item mentions booking and ipa_booking elaborates on it, but the descriptions make the boundary clear.
All tools consistently use the ipa_ prefix and lowercase snake_case, making the set predictable to scan. The names mix nouns (ipa_item, ipa_page) and verbs (ipa_find, ipa_search, ipa_open), so it is not a strict verb_noun convention, but the style is still coherent.
The 13 tools fit comfortably in the well-scoped range and each appears to earn its place across status, inventory, search, measurements, bookings, and file access. The surface is broad but not bloated.
Core workflows are covered: setup and user identity, equipment discovery, item and page lookup, search, laser/PSF measurements, builds, booking pointers, and library file listing/opening. Minor gaps remain around direct booking availability/calendar access and reading file contents rather than only listing/opening them, though browser/page workflows provide workarounds.