Weaviate MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug mode | false |
| MCP_USER_AGENT | No | Custom User-Agent for website fetching | |
| MCP_SERVER_HOST | No | Host to bind the server to | 0.0.0.0 |
| MCP_SERVER_PORT | No | Port to run the server on | 8000 |
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 |
|---|---|
| mcp_fetchC | Fetches a website and returns its content |
| moodA | Ask the server about its mood - it's always happy! |
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 completely distinct purposes: mcp_fetch is for fetching website content, while mood is a whimsical interaction unrelated to data operations. There is no overlap or ambiguity between them.
The naming is inconsistent: mcp_fetch follows a verb_noun pattern, but mood is a noun with no action verb. This mixing of conventions reduces predictability and clarity in the tool set.
With only 2 tools, the server feels severely under-scoped for a Weaviate MCP Server, which typically involves vector database operations like querying, indexing, or managing data. The tools provided do not align with the expected domain.
The tool surface is extremely incomplete for a Weaviate server. There are no tools for core vector database functions such as searching, adding data, or managing schemas, leaving significant gaps that would cause agent failures in this domain.