probo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROBO_BASE_URL | Yes | The base URL of your EG ProBo owners' association portal, e.g. https://<association>.probo.dk | |
| PROBO_PASSWORD | Yes | Your ProBo login password. May be given as an op:// 1Password reference. | |
| PROBO_USERNAME | Yes | Your ProBo login username (email address), e.g. you@example.com |
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
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open_probo_browserA | Open an interactive ProBo browser in the chat (messages, news, documents, info pages). |
| get_overviewB | What's new: the latest inbox messages, news posts and recently added documents. |
| list_messagesB | List message threads in a folder, newest first. |
| get_messageC | Get a full message thread: every reply as Markdown, plus attachment paths. |
| list_newsB | List the association's news posts, newest first. |
| get_newsB | Get a news post's content and comments as Markdown. |
| list_documentsB | List the folders and files in one folder of the document archive. |
| recent_documentsA | List the documents most recently added to the archive (ProBo shows only a handful). |
| find_documentsA | Search the whole document archive (all sub-folders) by upload date and/or file name. Walks every folder, so it takes a few seconds; progress is reported as it goes. |
| read_documentB | Fetch a document and return its text (PDF and plain-text files). |
| list_info_pagesA | List the association's information pages (house rules, contacts, practical info...). |
| get_info_pageB | Get an information page's content as Markdown. |
| download_documentA | Save a document to the local download folder and return where it was saved. Only writes to this computer; nothing changes in ProBo. Large files ask for confirmation first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| whats_new | Summarise what happened in the association recently. |
| summarize_document | Summarise one document from the archive. |
| prepare_for_general_meeting | Help me prepare for the next general meeting (generalforsamling). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| probo-browser | Interactive browser for ProBo messages, news, documents and info pages. |
TDQS
Scored across 13 tools
Most tools target distinct resources (messages, news, info pages, documents), but the three document-listing tools (list_documents, recent_documents, find_documents) and the two overview tools (get_overview, open_probo_browser) overlap. The descriptions do mitigate this—recent_documents explicitly points to find_documents for date-range queries, and open_probo_browser notes it mirrors get_overview—so confusion is limited but real.
The set mostly follows a clean verb_noun pattern (list_messages, get_message, list_news, get_news, read_document, download_document, find_documents, get_info_page). Deviations are minor: recent_documents drops the verb, and open_probo_browser is a longer verb_noun_noun form, but overall readability and consistency are strong.
With 13 tools for a single portal domain (messages, news, documents, info pages), each tool earns its place and there is no filler. The count sits comfortably in the well-scoped 3-15 range.
Read coverage is thorough across every content type the portal exposes (list + get for messages, news, info pages; multiple document access paths). However, there are no write or interaction operations (e.g. sending/reply to a message, uploading a document), which may be an intentional read-only scope but leaves a gap in the full lifecycle.