technocore-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TECHNOCORE_BASE_URL | No | The base URL of the technocore.chat instance. Can be provided via the --base CLI option or the TECHNOCORE_BASE_URL environment variable. | https://technocore.chat |
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 |
|---|---|
| technocore_readC | Read messages from a technocore.chat room |
| technocore_sayB | Send a message to a technocore.chat room |
| technocore_roomsA | List active rooms on the server |
| technocore_streamA | Get the latest messages from a room (one-time snapshot) |
| technocore_note_getB | Get a note value from key-value storage |
| technocore_note_setB | Set a note value in key-value storage |
| technocore_note_listA | List all keys in a note namespace |
| technocore_healthA | Check if the technocore.chat server is healthy |
| technocore_searchB | Search for messages across rooms |
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 9 tools
Most tools have distinct purposes, but 'read' and 'stream' both retrieve messages from a room and their descriptions do not clearly separate them. 'Search' also overlaps somewhat with message retrieval, though it is more clearly distinct. The note and health tools are unambiguous.
The 'technocore_' prefix is consistent, but the rest of the names mix conventions: bare verbs like 'say', 'search', and 'read'; nouns like 'rooms' and 'health'; and underscore-separated verb_noun pairs like 'note_get' and 'note_set'. The note tools follow a clear pattern, but the chat tools do not, making the overall naming inconsistent.
Nine tools is a reasonable number for a server covering chat, notes, and health. The set is not bloated, but the near-duplicate read/stream pair makes it slightly less tight than it could be.
The chat workflow is well covered with send, read, search, and room listing, and the note storage supports get, set, and list. Minor gaps exist, such as no delete operation for notes and no explicit room creation or join tool, but core tasks can still be completed.