Skip to main content
Glama
enesjakozh
filipecalegario

strateegia MCP Server

by filipecalegario
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

strateegia MCP Server

This is a Model Context Protocol (MCP) server that integrates with the strateegia API, allowing AI assistants like Claude or Cursor to access and interact with your strateegia projects.

Features

  • List all accessible strateegia projects

  • Access detailed information about labs and projects

Related MCP server: Apifox MCP Server

Prerequisites

  • Node.js (v16 or higher)

  • A valid strateegia API key

For Development

  1. Install dependencies:

npm install

  1. Build the project:

npm run build

  1. Set your strateegia API key as an environment variable:

export STRATEEGIA_API_KEY=your_api_key_here

  1. Start the server:

npm start

Connecting with Claude for Desktop

  1. Make sure you have Claude for Desktop installed.

  2. Create or edit your Claude for Desktop configuration file:

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

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

  1. Add the following configuration:

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

Connecting with Cursor

  1. Make sure you have Cursor installed.

  2. Open Cursor and go to the settings page.

  3. Add a new MCP server with the following configuration:

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

  1. Restart Cursor

Available Tools

The server exposes the following MCP tools:

  • list-projects: Lists all accessible projects and labs from your strateegia account

Contributing

Contributions are welcome! Feel free to submit a Pull Request.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Issues and Support

If you encounter any issues or need support, please file an issue on the GitHub repository.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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.
    969
    94
    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