Skip to main content
Glama
enesjakozh
filipecalegario

strateegia MCP Server

by filipecalegario
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

MCP 서버 전략

이는 strateegia API와 통합되는 MCP(Model Context Protocol) 서버로, Claude나 Cursor와 같은 AI 어시스턴트가 strateegia 프로젝트에 액세스하여 상호 작용할 수 있도록 해줍니다.

특징

  • 접근 가능한 모든 전략 프로젝트 나열

  • 연구실 및 프로젝트에 대한 자세한 정보에 액세스하세요

Related MCP server: Apifox MCP Server

필수 조건

  • Node.js(v16 이상)

  • 유효한 전략 API 키

개발을 위해

  1. 종속성 설치:

지엑스피1

  1. 프로젝트를 빌드하세요:

npm run build

  1. Strateegia API 키를 환경 변수로 설정하세요.

export STRATEEGIA_API_KEY=your_api_key_here

  1. 서버를 시작합니다:

npm start

데스크톱용 Claude와 연결

  1. Claude for Desktop이 설치되어 있는지 확인하세요.

  2. Claude for Desktop 구성 파일을 만들거나 편집하세요.

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

  1. 다음 구성을 추가합니다.

{
  "mcpServers": {
    "strateegia": {
      "command": "node",
      "args": ["path/to/strateegia-mcp-server/dist/index.js"],
      "env": {
        "STRATEEGIA_API_KEY": "your_api_key_here"
      }
    }
  }
}

커서로 연결하기

  1. 커서가 설치되어 있는지 확인하세요.

  2. 커서를 열고 설정 페이지로 이동합니다.

  3. 다음 구성으로 새로운 MCP 서버를 추가합니다.

env STRATEEGIA_API_KEY=your_api_key_here node path/to/strateegia-mcp-server/dist/index.js

  1. 커서 재시작

사용 가능한 도구

서버는 다음과 같은 MCP 도구를 제공합니다.

  • list-projects : Strateegia 계정에서 접근 가능한 모든 프로젝트와 랩을 나열합니다.

기여하다

기여를 환영합니다! 풀 리퀘스트를 제출해 주세요.

특허

이 프로젝트는 MIT 라이선스에 따라 라이선스가 부여되었습니다. 자세한 내용은 라이선스 파일을 참조하세요.

문제 및 지원

문제가 발생하거나 지원이 필요한 경우 GitHub 저장소 에 문제를 제출하세요.

Available Tools

1 tool
list-projectsB

List projects from Strateegia API

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

B3.1/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 full burden. It only states what the tool does ('List projects'), without disclosing behavioral traits like pagination, rate limits, authentication needs, or response format. This is inadequate for a tool with zero annotation coverage.

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 a single, efficient sentence with no wasted words, front-loading the core action. It's appropriately sized for a simple list tool, making it easy for an agent to parse quickly.

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 no annotations and no output schema, the description is incomplete. It lacks details on behavior, response format, or any context needed for effective use. For a tool with such minimal structured data, the description should provide more operational insight.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the inputs. The description doesn't need to add parameter details, and it appropriately doesn't mention any. Baseline is 4 for zero parameters, as no compensation is needed.

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 ('List') and resource ('projects from Strateegia API'), making the purpose understandable. It lacks sibling tools for differentiation, but the verb+resource combination is specific enough for a standalone tool. No tautology or misleading elements are present.

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, such as context, prerequisites, or alternatives. With no siblings mentioned, it doesn't need to differentiate, but it fails to offer any usage context, leaving the agent without direction on appropriate scenarios.

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. 1 tool update
    • First observedlist-projects
Deploy Server
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

TDQS

B3.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'list-projects' has a clear, singular purpose that cannot be confused with any other tool in the set.

Naming Consistency5/5

The single tool name 'list-projects' follows a consistent verb_noun pattern (list + projects). With only one tool, there is no inconsistency or deviation in naming conventions to evaluate.

Tool Count2/5

A single tool is generally too few for a server's purpose, as it severely limits functionality and suggests an incomplete or thin implementation. For a Strateegia API server, one tool does not provide adequate coverage for typical operations like creating, updating, or deleting projects, or managing other resources.

Completeness1/5

The tool set is severely incomplete for a Strateegia API server. With only a 'list-projects' tool, there are obvious gaps in CRUD operations (e.g., create, update, delete projects) and other essential functionalities like managing users, tasks, or reports, which are typical in project management domains.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Apifox MCP Server by apifox

    Apifox MCP Serverofficial

    apifox
    A
    license
    Not graded
    quality
    F
    maintenance
    A server that connects AI coding assistants like Cursor and Cline to Apifox API definitions, allowing developers to implement API interfaces through natural language commands.
    5,779 npm
    95
    ISC

  • Claudeus Plane MCP

    deus-h
    F
    license
    Not graded
    quality
    D
    maintenance
    A server that bridges Claude AI with the Plane project management platform, enabling AI-powered project management tasks including project creation, task management, team collaboration, and automated workflows.
    5
    -

Appeared in Searches