Skip to main content
Glama
juliengrelet

Wisembly MCP Server

by juliengrelet
README.md
# MCP Server Wisembly
### First step
This MCP Server is designed to interact with the Wisembly API. It provides a set of tools to fetch event data from the Wisembly API.

#### Setup

1. Clone the repository
2. Install the dependencies using 
```bash
npm install
```
3. Build the project 
```bash
npm run build
```

#### Tools

- `get_wisembly_event`: Fetch event data from the Wisembly API for any keyword (on PRP only for the moment)

#### Environment Variables

- `API_TOKEN`: Your Wisembly API token. This is required for several futurs endpoints (POST, GET, DELETE, etc…).

#### Error Handling

The server defines several custom error classes to handle different types of errors:

- `WisemblyApiError`: Base error class for all Wisembly API errors
- `WisemblyNotFoundError`: Thrown when an event is not found
- `WisemblyUnauthorizedError`: Thrown when unauthorized access to the Wisembly API is detected
- `WisemblyServerError`: Thrown when a server error occurs in the Wisembly API

#### Response Formatting

The server uses a custom response formatter to format the data returned from the Wisembly API. The formatter includes fields such as event ID, name, description, status, start date, end date, location, organizer, participants, and URL.

#### Configuration

```json
{
    "mcpServers": {
        "mcpWisembly": {
            "command": "/usr/local/bin/node",
            "args": ["/{your-path}/build/index.js"],
            "env": {
                "API_TOKEN": "your_api_token"
            }
        }
    }
}
```
#### Examples : 
[Lien 1](https://youtu.be/Pm3OWNuTWXA)
[Lien 2](https://youtu.be/zoWJfXctXCY)




TDQS

B3.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one fetches event data by keyword, while the other fetches session data by event ID. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the input parameter.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with 'get_wisembly_' prefix, using snake_case throughout. The naming is predictable and readable, with no deviations in style or convention.

Tool Count2/5

With only 2 tools, the server feels thin for a Wisembly API integration. This minimal set lacks essential operations like creating, updating, or deleting events/sessions, limiting its utility for comprehensive agent workflows in this domain.

Completeness2/5

The tool surface is severely incomplete for a Wisembly API server. It only provides read operations (get_event and get_sessions), missing critical CRUD functionality such as create_event, update_event, delete_event, and session management operations, which are essential for full lifecycle coverage.

Maintenance

ActivityInactive
ResponsivenessNo issues