Wisembly MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_TOKEN | Yes | Your Wisembly API token. This is required for several future endpoints (POST, GET, DELETE, etc…). |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_wisembly_eventC | Fetch event data from the Wisembly API for any keyword |
| get_wisembly_sessionsC | Fetch sessions data from the Wisembly API by event id |
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 2 tools
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.
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.
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.
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.