@mnicole-dev/erezo-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EREZO_API_KEY | Yes | Your eRezo API key | |
| EREZO_API_URL | No | API base URL (for development) | https://www.erezo.fr |
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_contactsA | List contacts with optional search, filtering by status, and sorting. Returns paginated results. |
| get_contactA | Get detailed information about a specific contact by its UUID. |
| create_contactA | Create a new contact. Subject to quota limits (freemium: 20 max, premium: 30/day). |
| update_contactA | Update an existing contact. Only provided fields are modified (partial update). |
| delete_contactA | Permanently delete a contact by its UUID. |
| search_contactsA | Quick search across contacts by name, email, or company. Returns the first page of matching results. |
| list_eventsA | List upcoming events with optional filters by organizer, department, or date range. Returns paginated results. |
| get_eventA | Get detailed information about a specific event by its ID. |
| register_eventA | Register the current user for an event. Fails if the event is cancelled, past, or full. |
| unregister_eventA | Cancel the current user's registration for an event. |
| get_meA | Get the current authenticated user's profile information including name, email, company, and roles. |
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 11 tools
Tools are mostly distinct with clear CRUD actions for contacts and events. The only potential confusion is between list_contacts and search_contacts, as both allow searching contacts, but list_contacts is more comprehensive with filters and pagination while search_contacts is a quick search. This is a minor overlap.
All tools follow a consistent verb_noun naming pattern using snake_case, such as list_contacts, get_event, register_event, and get_me. The pattern is uniform and predictable.
With 11 tools, the server is well-scoped for its apparent purpose of contact and event management. Each tool serves a distinct function, and the count fits within the ideal 3-15 range.
The contact domain has full CRUD plus search, and the event domain covers listing, retrieval, registration, and unregistration. get_me provides user context. No obvious missing operations for the intended workflow.