open-index/open-npm huggingface dataset:
npm package: @iflow-mcp/groq-compound-mcp-server
Description: MCP server for interacting with Groq models
Author: Rick Lamers
Latest version: 0.1.7

# groq-compound-mcp-server

Provides a Model Context Protocol (MCP) server for interacting with Groq models, including compound/meta models.

This server exposes the following tools:
*   `ask_with_realtime_information`
*   `ask_with_code_execution`

## Prerequisites

*   Node.js >= 18.0.0
*   A Groq API key set in the `GROQ_API_KEY` environment variable.

## Installation

```bash
npm install groq-compound-mcp-server
```

## Usage

This server follows the standard MCP server pattern using stdio for transport. It's designed to be run by an MCP client (like Claude Desktop or a custom client).

Refer to the official [MCP Quickstart for Server Developers](https://modelcontextprotocol.io/quickstart/server) for instructions on setting up and connecting MCP servers.

When configuring your client, use the command `npx groq-compound-mcp-server` or `groq-compound-mcp-server` (if installed globally) to run this server.

Here's an example of how you might configure an MCP client (e.g., in a `settings.json` file) to launch this server:

```json
{
  "mcpServers": {
    "groq-compound": {
      "command": "npx",
      "args": [
        "-y",
        "groq-compound-mcp-server"
      ],
      "env": {
        "GROQ_API_KEY": "YOUR_GROQ_API_KEY_HERE"
      }
    }
  }
}
```

## Hosting on Vercel

This server can also be deployed to Vercel.

1.  **Prerequisites**:
    *   Ensure you have a Vercel account.
    *   Connect your Git repository to Vercel.

2.  **Environment Variables**:
    Set the following environment variables in your Vercel project settings:
    *   `GROQ_API_KEY`: Your Groq API key.
    *   `REDIS_URL`: (Recommended for SSE transport) The connection URL for a Redis instance (e.g., from Vercel KV or Upstash).

3.  **Build Configuration**:
    Vercel should automatically detect it as a Next.js application. The build command `npm run build:vercel` (or `yarn build:vercel`/`pnpm build:vercel`) and the output directory (`.next`) will be used.

4.  **Accessing the MCP Server**:
    Once deployed, your MCP server endpoints will be available at `https://your-deployment-url.vercel.app/api/mcp`.
    For example, the SSE endpoint would be `https://your-deployment-url.vercel.app/api/mcp/sse`.

## Development with Vercel CLI

To run the Vercel deployment locally:

1.  Install Vercel CLI: `npm install -g vercel`
2.  Set up environment variables locally (e.g., in a `.env.local` file at the project root):
    ```
    GROQ_API_KEY=your_groq_api_key
    REDIS_URL=your_redis_url
    ```
3.  Run the development server: `vercel dev` or `npm run dev:vercel`.

## License

[MIT](LICENSE)
npm package: @iflow-mcp/growthbook-growthbook-mcp
Description: MCP Server for interacting with GrowthBook
Author: GrowthBook
Latest version: 1.8.1

# GrowthBook MCP Server

With the GrowthBook MCP server, you can interact with GrowthBook right from your LLM client. See experiment details, add a feature flag, and more.

<a href="https://glama.ai/mcp/servers/@growthbook/growthbook-mcp">
  <img width="380" height="200" src="https://glama.ai/mcp/servers/@growthbook/growthbook-mcp/badge" alt="GrowthBook Server MCP server" />
</a>

## Setup

**Environment Variables**
Use the following env variables to configure the MCP server.

| Variable Name | Status   | Description                                                       |
| ------------- | -------- | ----------------------------------------------------------------- |
| GB_API_KEY    | Required | A GrowthBook API key or PAT. When using a PAT, MCP server capabilities are limited by its permissions. E.g., if the user can't create an experiment in the app, they also won't be able to create one with the MCP server.                                             |
| GB_EMAIL      | Required | Your email address used with GrowthBook. Used when creating feature flags and experiments.|
| GB_API_URL    | Optional | Your GrowthBook API URL. Defaults to `https://api.growthbook.io`. |
| GB_APP_ORIGIN | Optional | Your GrowthBook app URL Defaults to `https://app.growthbook.io`.  |
| GB_HTTP_HEADER_* | Optional | Custom HTTP headers to include in all GrowthBook API requests. Use the pattern `GB_HTTP_HEADER_<NAME>` where `<NAME>` is converted to proper HTTP header format (underscores become hyphens). Examples: `GB_HTTP_HEADER_X_TENANT_ID=abc123` becomes `X-Tenant-ID: abc123`, `GB_HTTP_HEADER_CF_ACCESS_TOKEN=<token>` becomes `Cf-Access-Token: <token>`. Multiple custom headers can be configured. |

Add the MCP server to your AI tool of choice. See the [official docs](https://docs.growthbook.io/integrations/mcp) for complete a complete guide.
npm package: @iflow-mcp/gtrias_i18next-mcp-server
Description: A comprehensive Model Context Protocol (MCP) server for i18next translation management, health checking, and automated translation workflows
Author: Genar Trias
Latest version: 1.1.0

# i18next MCP Server

[![npm version](https://badge.fury.io/js/i18next-mcp-server.svg)](https://badge.fury.io/js/i18next-mcp-server)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

A Model Context Protocol (MCP) server that provides translation management capabilities for i18next projects, enabling AI assistants like Cursor to directly interact with translation files.

## 🚀 Quick Setup

The easiest way to use this MCP server is with npx. No installation required:

```bash
npx i18next-mcp-server@latest --help
```

## 🔧 Cursor Configuration

Add this to your Cursor MCP settings:

```json
{
  "mcpServers": {
    "i18next-translation": {
      "command": "npx",
      "args": ["-y", "i18next-mcp-server@latest"],
      "env": {
        "I18N_PROJECT_ROOT": "/path/to/your/project",
        "I18N_LOCALES_PATH": "public/locales",
        "I18N_DEFAULT_LANGUAGE": "en",
        "I18N_SUPPORTED_LANGUAGES": "en,es,fr"
      }
    }
  }
}
```

For detailed setup instructions, see [CURSOR_SETUP.md](./CURSOR_SETUP.md).

## 📁 Expected Project Structure

```
your-project/
├── public/locales/          # Translation files
│   ├── en/
│   │   ├── common.json
│   │   └── navigation.json
│   ├── es/
│   │   ├── common.json
│   │   └── navigation.json
│   └── ...
└── src/                     # Your source code
```

## 🛠️ Available Tools

### Core Tools
- **`get_project_info`** - Get project configuration and statistics
- **`health_check`** - Analyze translation file health and completeness
- **`scan_code_for_missing_keys`** - Find missing translation keys in your code

### Key Management
- **`add_translation_key`** - Add new translation keys
- **`sync_missing_keys`** - Sync missing keys between languages
- **`get_missing_keys`** - List missing keys by language

### File Operations
- **`list_files`** - List all translation files
- **`validate_files`** - Validate JSON syntax
- **`export_data`** - Export translations to various formats

### Analysis
- **`coverage_report`** - Translation coverage statistics
- **`usage_analysis`** - Find unused translation keys
- **`quality_analysis`** - Analyze translation quality

## 🔧 Environment Variables

| Variable | Description | Default |
|----------|-------------|---------|
| `I18N_PROJECT_ROOT` | Your project root directory | Current directory |
| `I18N_LOCALES_PATH` | Path to translation files | `public/locales` |
| `I18N_DEFAULT_LANGUAGE` | Source language | `en` |
| `I18N_SUPPORTED_LANGUAGES` | Comma-separated language codes | `en` |

## 🧪 Development

```bash
git clone https://github.com/gtrias/i18next-mcp-server.git
cd i18next-mcp-server
npm install
npm run build
npm test
```

## 📝 License

MIT License - see [LICENSE](LICENSE) for details.

## 🔗 Links

- [Setup Guide](./CURSOR_SETUP.md)
- [Contributing](./CONTRIBUTING.md)
- [Issues](https://github.com/gtrias/i18next-mcp-server/issues)