digihub-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DIGIHUB_BASE_URL | Yes | The base URL of the digihub.li instance, e.g. https://digihub.li | |
| DIGIHUB_API_TOKEN | Yes | A Sanctum personal access token that encodes permissions (treat like a password) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_storiesC | List stories with optional filters. |
| get_storyA | Fetch a single story by slug. |
| create_storyC | Create a new story. |
| update_storyB | Update an existing story by slug. |
| delete_storyC | Soft-delete a story by slug. |
| list_solutionsC | List solutions with optional filters. |
| get_solutionC | Fetch a single solution by slug. |
| create_solutionD | Create a new solution. |
| update_solutionC | Update an existing solution by slug. |
| delete_solutionC | Soft-delete a solution by slug. |
| list_sessionsC | List sessions (events) with optional filters. |
| get_sessionB | Fetch a single session by slug. |
| create_sessionC | Create a new session (event). |
| update_sessionC | Update an existing session by slug. |
| delete_sessionB | Soft-delete a session by slug. |
| upload_mediaB | Upload a local file or have the server fetch a remote URL. Returns a |
| whoamiA | Returns the authenticated user and the abilities granted to the current token. |
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 17 tools
Every tool targets a distinct resource-action pair (create/get/list/update/delete for sessions, solutions, and stories). There is no overlap, as the resource noun clearly differentiates each tool.
All tools follow a consistent verb_noun pattern (e.g., create_session, delete_solution, list_stories) using snake_case. No deviations or mixed conventions.
With 17 tools covering three core entities plus media upload and authentication, the count is well-scoped for a digital hub server. Each tool serves a clear purpose without unnecessary bloat.
Full CRUD lifecycle is provided for sessions, solutions, and stories. The upload_media and whoami tools fill common needs, leaving no obvious gaps for the server's stated domain.