Skip to main content
Glama
Lodestar MCP Server

Lodestar MCP Server

by kanlanc

To start the project

uv venv
uv sync
mcp dev server.py

After every change in the code, you need to re run

mcp dev server.py

NOTE: You should look into how to do hot reloads

Look into how the other example mcp servers are running with their respective tool exposing

Potential next steps:

  • Should I expose API Keys and stuff as a resource or should i make the platform url as a resource

  • one of the tools should be getting a new api_key and project_id for the user if they dont have it for the current one but I need to get the right user somehow

  • Look into how the other tools are doing this stuff

Write mcp prompts that help llms understand how to write the prompts for best results

Servers to look at:

Looks lke most of these are using ts, maybe I should also change gears to that

Actually I dont see why typescript would be better especially in our usecase, so sticking to better readbility python might be better

Potential Contributions

Hot reload when the developer writes code to MCP

Available Tools

1 tool
doc_queryC

Query project documentation.

Args:
    query (str): The query text from the user
    api_key (str): Authentication key for the request
    project_id (str): Identifier for the target project
    
Returns:
    ContextResponse: The generated response

Inputs: query (required), api_key (required), project_id (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'doc_query' has a clearly defined purpose that cannot be confused with any other tool in the set.

    Naming Consistency5/5

    The single tool name 'doc_query' follows a clear verb_noun pattern. With only one tool, the naming is inherently consistent as there are no other tools to compare against or create inconsistencies with.

    Tool Count2/5

    A single tool feels thin for a documentation query server, suggesting limited functionality. While it might be appropriate for a minimal prototype, a production documentation server would typically offer multiple operations like search, browse, filter, or manage documentation, making this count borderline inadequate.

    Completeness2/5

    The tool surface is severely incomplete for a documentation domain. While 'doc_query' covers querying, there are obvious gaps: no tools for listing available documentation, managing documentation sets, filtering by categories, or handling documentation updates. This will likely cause agent failures when trying to perform comprehensive documentation tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A template/boilerplate MCP server for building custom tools and integrations that enable seamless connections between AI applications and external data sources.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that allows users to define custom tools via a configuration file for tasks such as retrieving project architecture and managing task lists. It also includes a plugin for generating structured and optimized AI prompts based on specific context sections and instructions.
      2
      MIT