BrianKnows MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRIAN_API_KEY | Yes | Your BrianKnows API key |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Check if the Brian API server is alive |
| searchC | Search using Brian's knowledge engine |
| agentC | Chat with Brian agent |
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 3 tools
Each tool has a clearly distinct purpose with no overlap: 'agent' is for chatting with an AI agent, 'ping' is for health checking the API server, and 'search' is for querying a knowledge engine. The descriptions make it easy to differentiate these functions, eliminating any risk of misselection.
The naming is mixed in style: 'agent' and 'ping' are simple verbs, while 'search' is a verb that could fit a pattern, but there is no consistent verb_noun structure or uniform convention. However, the names are readable and straightforward, avoiding chaotic or confusing formats.
With only 3 tools, the count feels thin for a server named 'BrianKnows MCP Server', which suggests a broader knowledge or interaction domain. While the tools cover basic operations (chat, health check, search), it may lack depth for more complex workflows, making it borderline in scope.
The tool surface has significant gaps for a knowledge-oriented server: there is no way to create, update, or manage knowledge entries, and the 'agent' tool lacks clarity on its capabilities beyond chatting. This incompleteness could lead to agent failures when trying to perform comprehensive tasks in the domain.