indico-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INDICO_URL | No | The URL of the Indico server (for single server mode). | |
| INDICO_TOKEN | No | Personal token for the Indico server (for single server mode). Used for write operations. | |
| INDICO_INSTANCES | No | Comma-separated list of name=url pairs for multiple Indico servers (e.g., cern=https://indico.cern.ch,in2p3=https://indico.in2p3.fr). | |
| INDICO_READ_ONLY | No | Set to 'true' to remove every write tool. | |
| INDICO_UPLOAD_DIR | No | Directory allowed for file uploads. | |
| INDICO_ALLOW_DELETE | No | Set to 'true' to enable delete tools. |
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 |
|---|---|
| indico_list_instancesA | List the Indico instances this server can reach; pass a name as |
| indico_whoamiA | Return the Indico user the token belongs to (null when anonymous). |
| indico_search_eventsA | Search events by title. Only returns events the token's user can see. |
| indico_list_category_eventsB | List events in a category (and its subcategories) within a date range. |
| indico_get_eventB | Get an event's details: dates, location, chairs, material, and optionally contributions or sessions. |
| indico_get_timetableA | Get an event's timetable as a flat list of entries in start order. |
| indico_list_contributionsA | List all contributions of an event with database ids, session, schedule and people. Needs management rights on the event. |
| indico_list_registration_formsA | List an event's registration forms with registration counts. Needs the 'Registrants' token scope. |
| indico_list_registrationsB | List registrations of a registration form (state, payment, check-in, tags). |
| indico_get_registrationB | Get one registration, including the answers to the form fields. |
| indico_create_eventC | Create a meeting or conference and return its id. |
| indico_update_eventA | Change an event's title, description, dates or location. Fields left out keep their value. Changing dates also shifts the timetable, as the Indico UI does by default. |
| indico_create_sessionA | Create a session. It has no time slot until you add one with indico_create_session_block. |
| indico_update_sessionC | Change a session's title, description, code or default contribution length. |
| indico_create_session_blockA | Add a time slot (session block) for a session to the timetable; contributions of the session go inside it. |
| indico_update_session_blockA | Change a session block's duration or title. It cannot become shorter than the entries inside it. |
| indico_create_contributionA | Create an unscheduled contribution. Use indico_schedule_contribution to place it in the timetable. |
| indico_update_contributionB | Change a contribution's title, description, duration or people. Fields left out keep their value. |
| indico_assign_contribution_sessionA | Move a contribution into a session, or out of it. Indico may unschedule it if its slot no longer fits. |
| indico_schedule_contributionA | Put an unscheduled contribution in the timetable at a given time. |
| indico_move_timetable_entryB | Change the start time of a timetable entry (contribution or session block). |
| indico_unschedule_timetable_entryA | Remove an entry from the timetable. |
| indico_add_linkB | Attach a link (slides, recording, document) to an event, a session or a contribution. |
| indico_set_checkinB | Mark a registrant as checked in at the venue, or undo it. |
| indico_moderate_registrationA | Approve or reject a pending registration. Indico emails the registrant either way. |
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 25 tools
Most tools target distinct resources and actions, and descriptions clarify ambiguous boundaries (e.g., scheduling vs moving vs assigning contributions). Minor overlap remains between get_event's optional sub-lists and dedicated list tools, and between timetable movement and update operations, but these are manageable.
All tools use the consistent indico_ prefix and snake_case verb_noun pattern (e.g., indico_create_event, indico_list_contributions). The only slight outlier is indico_whoami, but it remains readable and does not disrupt the overall convention.
With 25 tools, the surface is heavy for an MCP server, exceeding the typical 3-15 sweet spot. While each tool maps to a distinct operation in a complex event-management domain, the total risks overwhelming agents and could likely be consolidated.
Core workflows for events, sessions, contributions, timetable, and registration are covered, but explicit delete operations for events, sessions, and contributions are missing (deletion is only partly folded into unschedule behavior). Single-resource getters for sessions, contributions, and session blocks are also absent, creating notable lifecycle gaps.