Lodestar MCP Server
프로젝트를 시작하려면
지엑스피1
uv syncmcp dev server.py코드를 변경할 때마다 다시 실행해야 합니다.
mcp dev server.py참고: 핫 리로드 방법을 살펴보세요.
다른 예제 mcp 서버가 각각의 도구를 노출하여 어떻게 실행되는지 살펴보세요.
다음 단계:
API 키와 기타 항목을 리소스로 노출해야 합니까? 아니면 플랫폼 URL을 리소스로 만들어야 합니까?
도구 중 하나는 현재 사용자에게 api_key와 project_id가 없는 경우 해당 사용자의 새 api_key와 project_id를 가져오는 것이어야 하지만 어떻게든 올바른 사용자를 가져와야 합니다.
다른 도구가 이 작업을 어떻게 수행하는지 살펴보세요.
LLM이 최상의 결과를 얻기 위해 프롬프트를 작성하는 방법을 이해하는 데 도움이 되는 MCP 프롬프트를 작성하세요.
살펴볼 서버:
대부분이 ts를 사용하는 것 같은데, 나도 그걸로 바꿔야 할 것 같아요.
사실 저는 TypeScript가 특히 우리의 사용 사례에서 더 나을 이유를 모르겠습니다. 따라서 더 나은 가독성을 고수하는 Python이 더 나을 수도 있습니다.
잠재적 기여
개발자가 MCP에 코드를 작성할 때 핫 리로드
Available Tools
1 tooldoc_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
Scored across 1 tool
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.
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.
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.
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
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
MCP server for generating rough-draft project plans from natural-language prompts.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA production-ready MCP server built with FastAPI, providing an enhanced tool registry for creating, managing, and documenting AI tools for Large Language Models (LLMs).34-
- FlicenseNot gradedqualityDmaintenanceA template/boilerplate MCP server for building custom tools and integrations that enable seamless connections between AI applications and external data sources.-
- AlicenseNot gradedqualityDmaintenanceAn 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.2MIT
- FlicenseNot gradedqualityCmaintenanceA Python MCP server providing AI agents with tools for local knowledge base search, business context retrieval, and text summarization prompt generation.-