EGIPCI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EGIPCI_COOKIE | Yes | The .intranet cookie for EGIPCI authentication. |
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 |
|---|---|
| query_egipci_siteB | Query archaeological site information from the EGIPCI service of the Generalitat de Catalunya |
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 1 tool
Only one tool exists, so there is no possibility of confusion or overlap.
The single tool name follows a clear verb_noun pattern (query_egipci_site), establishing a consistent convention.
With only one tool for what likely requires multiple operations (e.g., query, list, detail), the surface feels insufficient for a well-scoped server.
The server provides only a query capability; without create, update, or delete tools, it is incomplete for typical archaeological site management.