Skip to main content
Glama
deenesjakoruzh
kirill-markin

Weaviate MCP Server

by kirill-markin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

MCP Server Template for Cursor IDE

Una plantilla sencilla para crear herramientas personalizadas para Cursor IDE mediante el Model Context Protocol (MCP). Crea tu propio repositorio a partir de esta plantilla, modifica las herramientas y conéctalas a tu Cursor IDE.

Respuesta del estado de ánimo del servidor

Inicio rápido

  1. Haz clic en el botón «Desplegar en Heroku»

    Desplegar en Heroku

  2. Después del despliegue, configura Cursor:

    • Abre Configuración de Cursor → Funciones

    • Añade un nuevo servidor MCP

    • Usa tu URL de Heroku con la ruta /sse (p. ej., https://<your-app-name>.herokuapp.com/sse)

  3. Prueba el estado de ánimo de tu agente en Cursor:

    • Pregunta a tu agente «Por favor, pregunta por el estado de ánimo de nuestro servidor y dime cómo está.»

    • El servidor responderá con un mensaje alegre y un corazón ❤️

Related MCP server: pure.md MCP server

Métodos de configuración alternativos

Puedes ejecutar el servidor de tres formas: usando Docker, con la configuración tradicional de Python o directamente en Cursor IDE.

Configuración con Docker

El proyecto incluye soporte para Docker para facilitar el despliegue:

  1. Configuración inicial:

# Clone the repository
git clone https://github.com/kirill-markin/weaviate-mcp-server.git
cd weaviate-mcp-server

# Create environment file
cp .env.example .env

  1. Construye y ejecuta usando Docker Compose:

# Build and start the server
docker compose up --build -d

# View logs
docker compose logs -f

# Check server status
docker compose ps

# Stop the server
docker compose down

  1. El servidor estará disponible en:

  2. Prueba rápida:

# Test the server endpoint
curl -i http://localhost:8000/sse

  1. Conecta con Cursor IDE:

    • Abre Configuración de Cursor → Funciones

    • Añade un nuevo servidor MCP

    • Tipo: Selecciona «sse»

    • URL: Introduce http://localhost:8000/sse

Configuración tradicional

Primero, instala el gestor de paquetes uv:

# Install uv on macOS
brew install uv
# Or install via pip (any OS)
pip install uv

Inicia el servidor usando transporte stdio (por defecto) o SSE:

# Install the package with development dependencies
uv pip install -e ".[dev]"

# Using stdio transport (default)
uv run mcp-simple-tool

# Using SSE transport on custom port
uv run mcp-simple-tool --transport sse --port 8000

# Run tests
uv run pytest -v

Después de la instalación, puedes conectar el servidor directamente a Cursor IDE:

  1. Haz clic derecho en el archivo cursor-run-mcp-server.sh en Cursor

  2. Selecciona «Copiar ruta» para copiar la ruta absoluta

  3. Abre Configuración de Cursor (icono de engranaje)

  4. Ve a la pestaña Funciones

  5. Desplázate hacia abajo hasta «Servidores MCP»

  6. Haz clic en «Añadir nuevo servidor MCP»

  7. Rellena el formulario:

    • Nombre: Elige cualquier nombre (p. ej., «my-mcp-server-1»)

    • Tipo: Selecciona «stdio» (no «sse» porque ejecutamos el servidor localmente)

    • Comando: Pega la ruta absoluta a cursor-run-mcp-server.sh que copiaste antes. Por ejemplo: /Users/yourname/weaviate-mcp-server/cursor-run-mcp-server.sh

Variables de entorno

Variables de entorno disponibles (se pueden configurar en .env):

  • MCP_SERVER_PORT (por defecto: 8000) - Puerto en el que se ejecuta el servidor

  • MCP_SERVER_HOST (por defecto: 0.0.0.0) - Host al que vincular el servidor

  • DEBUG (por defecto: false) - Activa el modo de depuración

  • MCP_USER_AGENT - User-Agent personalizado para la obtención de sitios web

Opciones adicionales

Instalación mediante Smithery

Para instalar MCP Server Template for Cursor IDE para Claude Desktop automáticamente mediante Smithery:

npx -y @smithery/cli install @kirill-markin/example-mcp-server --client claude

Reseña del servidor Glama

Available Tools

2 tools
mcp_fetchC

Fetches a website and returns its content

NameRequiredDescriptionDefault
urlYesURL to fetch

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool fetches and returns content, but lacks details on error handling, rate limits, authentication needs, or response format. For a tool with no annotations, this is a significant gap in transparency about its operational behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise and front-loaded, consisting of a single, clear sentence: 'Fetches a website and returns its content'. Every word earns its place, with no redundant or unnecessary information, making it efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a fetch operation with potential behavioral nuances), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'content' includes (e.g., HTML, text), error cases, or limitations, leaving gaps in understanding how the tool behaves in practice.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, with the parameter 'url' fully documented in the schema. The description adds no additional meaning beyond the schema, such as URL format constraints or examples. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't enhance parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('fetches') and resource ('a website'), specifying what the tool does. It distinguishes from most siblings (e.g., 'apply_prompt_' tools, 'mood') by focusing on web content retrieval, though it doesn't explicitly differentiate from 'fetch_railway_docs' tools. The purpose is specific but lacks sibling comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention scenarios for usage, prerequisites, or exclusions, and offers no comparison to sibling tools like 'fetch_railway_docs' or 'fetch_railway_docs_optimized'. Usage is implied only by the action 'fetches', with no explicit context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

moodA

Ask the server about its mood - it's always happy!

NameRequiredDescriptionDefault
questionYesAsk this MCP server about its mood! You can phrase your question in any way you like - 'How are you?', 'What's your mood?', or even 'Are you having a good day?'. The server will always respond with a cheerful message and a heart ❤️

TDQS

A3.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: the tool queries the server's mood, the server is 'always happy', and responses include 'a cheerful message and a heart ❤️'. This covers the interactive nature and predictable output style, though it lacks details like response format or error handling. No contradiction with annotations exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence) and front-loaded with the core purpose. Every word earns its place: 'Ask the server about its mood' defines the action, and 'it's always happy!' adds essential behavioral context. There's zero redundancy or fluff, making it highly efficient for an agent to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (single parameter, no output schema, no annotations), the description is reasonably complete for its purpose. It explains what the tool does and the expected response behavior. However, it lacks output details (e.g., response structure) and doesn't address potential edge cases, leaving some gaps in full contextual understanding for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the parameter 'question' fully documented in the schema itself (including examples like 'How are you?'). The description adds no additional parameter semantics beyond what the schema provides, such as formatting tips or constraints. According to rules, with high schema coverage (>80%), the baseline is 3 even without param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: to ask the server about its mood, with the specific behavioral outcome that it 'always responds with a cheerful message and a heart ❤️'. It distinguishes from sibling tools (all related to prompt application or documentation fetching) by focusing on a conversational interaction rather than functional operations. However, it doesn't explicitly contrast with specific alternatives for mood-checking, keeping it at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. While it implies usage for checking server mood, it doesn't specify contexts (e.g., after errors, during idle time) or exclusions (e.g., not for functional queries). With sibling tools focused on practical tasks, the lack of when/when-not guidance leaves the agent guessing about appropriate use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • First observedmcp_fetch
    • First observedmood
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

C2.8/5.0

Scored across 2 tools

Disambiguation5/5

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.

Naming Consistency2/5

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.

Tool Count2/5

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.

Completeness1/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • pure.md MCP server by puremd

    pure.md MCP serverofficial

    puremd
    A
    license
    D
    quality
    D
    maintenance
    An MCP server that enables AI clients like Cursor, Windsurf, and Claude Desktop to access web content in markdown format, providing web unblocking and searching capabilities.
    2
    6 npm
    60
    MIT

  • MCP Website Fetcher

    electrocucaracha
    F
    license
    Not graded
    quality
    F
    maintenance
    A lightweight MCP server implementation that provides a simple tool for fetching website content, demonstrating how tools can be exposed and interacted with using the MCP protocol.
    -

  • superFetch MCP Server

    j0hanz
    A
    license
    A
    quality
    C
    maintenance
    An MCP server that fetches web pages and extracts clean, AI-friendly Markdown content using Mozilla Readability. It provides secure web access for LLMs with built-in SSRF protection and automated content cleaning for improved context retrieval and summarization.
    1
    107 npm
    MIT

Appeared in Searches