Strateegia

Model Context Protocol for strateegia API

typescript

0

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

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

You run a Model Context Protocol (MCP) server that plugs into strateegia, letting AI assistants access and interact with your strateegia projects. It exposes a simple set of tools to list projects and inspect labs and projects, while keeping your API access secure via an API key.

How to use

Connect your MCP client (Claude Desktop or Cursor) to the server to access your strateegia data. The server provides a list of all accessible projects and detailed information about labs and projects. You control access with your strateegia API key, which you provide to the MCP server at runtime or through your client configuration.

How to install

Prerequisites: Node.js (v16 or higher) and a valid strateegia API key.

npm install

npm run build

export STRATEEGIA_API_KEY=your_api_key_here

npm start

Note: On Windows, use a Windows-compatible command to set the environment variable, for example:

set STRATEEGIA_API_KEY=your_api_key_here
`

Configuration and using with MCP clients

Configure your MCP client to connect to this server using the following examples. These configurations assume you have the STRATEEGIA_API_KEY environment variable available to the server.

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

"```

Note: The exact path to the built MCP server bundle may vary depending on your project structure. Ensure the node command runs the built entry point and that the STRATEEGIA_API_KEY is available to the process.

## Notes and troubleshooting

If you run into authentication issues, verify that the STRATEEGIA\_API\_KEY is correct and that the key has access to the projects you expect to query. Check that the MCP server process has the environment variable set when it starts. If the server fails to start, ensure you ran the build step so the dist/index.js file exists at the specified path.

## Available tools

### list-projects

Lists all accessible strateegia projects and labs from your account