ibabs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IBABS_SITE | Yes | Tenant/site name, e.g. example-site. | |
| IBABS_EMAIL | Yes | Login e-mail address. | |
| IBABS_PASSWORD | No | Login password. Provide either IBABS_PASSWORD or IBABS_SESSION_COOKIE. | |
| IBABS_CACHE_DIR | No | Where the session is cached. Defaults to the OS cache dir. | |
| IBABS_CLIENT_ID | No | OAuth client id. Defaults to the public iBabs portal client. | |
| IBABS_LOGIN_URL | No | Defaults to https://signon.ibabs.eu. | https://signon.ibabs.eu |
| IBABS_PORTAL_URL | No | Defaults to https://portal.ibabs.eu. | https://portal.ibabs.eu |
| IBABS_DOWNLOAD_DIR | No | Where attachments are written. Defaults to <cache>/downloads. | |
| IBABS_REDIRECT_URI | No | OAuth redirect. Defaults to https://portal.ibabs.eu/signin-iBabs. | https://portal.ibabs.eu/signin-iBabs |
| IBABS_AUTHORIZE_URL | No | Defaults to https://signon.ibabs.eu/OAuth/Authorize. | https://signon.ibabs.eu/OAuth/Authorize |
| IBABS_SESSION_COOKIE | No | A pre-existing __Host-ibabsportal cookie value, instead of password. Provide either IBABS_PASSWORD or IBABS_SESSION_COOKIE. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_meetingsA | List your iBabs meetings in a date range, in chronological order. Defaults to the next 30 days. Use type 'council' to only get council/committee meetings. |
| get_meetingA | Get one meeting by id, including its agenda items with their number, title, confidentiality flag and attachments with name and size. Also includes meeting-level attachments that are not tied to an agenda item. |
| get_attachmentB | Download an attachment by documentId and return its name, mime type and local path. PDFs and text files are also returned as extracted text. |
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 3 tools
list_meetings lists meetings, get_meeting retrieves one meeting's full details, and get_attachment downloads a specific attachment. Each tool targets a distinct resource and action with no overlap.
All three tools follow a consistent snake_case verb_noun pattern: list_meetings, get_meeting, get_attachment. The convention is predictable and readable.
Three tools is minimal but well-suited for a read-only API focused on meetings and attachments. Each tool earns its place, though the surface is slightly thin for the broader domain.
The set covers listing meetings, retrieving a meeting with agenda items and attachments, and downloading attachments. Minor gaps include no search or filtering beyond date and type, but core read-only workflows are covered.