gemsAPI

KO | EN

gitlite — search

#javascript #python #hacktoberfest #llm #go #machine-learning #linux #java #awesome #awesome-list #pytorch #security #mcp #open-source

(★ 13)

A FastAPI and MCP server connected to Supabase table for managing, testing, and programmatically accessing LLM System Instructions, System Prompts, BOTs, Google Gems.

gemsAPI 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# gemsAPI

[![TypeScript](https://img.shields.io/badge/TypeScript-5.8-blue)](https://www.typescriptlang.org/)
[![FastAPI](https://img.shields.io/badge/FastAPI-0.115-green)](https://fastapi.tiangolo.com/)
[![React](https://img.shields.io/badge/React-19-cyan)](https://react.dev/)
[![License](https://img.shields.io/badge/License-MIT-yellow.svg)](https://raw.githubusercontent.com/sruckh/gemsAPI/main/LICENSE)

> A full-stack interface for managing and executing custom AI instructions ("Gems") with Supabase auth, Gemini multimodal chat, and optional MCP integration.

Since the standard Gemini Gems interface does not currently support direct API access, gemsAPI provides a backend service and web UI for storing, managing, and executing custom AI prompts with current Gemini text and image-capable models.

## ✨ Features

- **Gem Management**: Create, edit, and delete custom AI instruction sets ("Gems") stored in Supabase
- **Authenticated Web UI**: Google OAuth via Supabase with admin detection and protected CRUD/API access
- **Flexible Execution**: Execute Gems by name or via free-form generation with custom prompts
- **Multimodal Chat**: Upload or drag/drop image attachments into chat and send them to Gemini
- **Inline Image Display**: Render generated Gemini image parts directly inside the chat thread
- **Model Routing**: Use separate configurable default models for text chat and image-capable chat
- **MCP Integration**: Model Context Protocol (MCP) server for Claude Desktop and other MCP clients
- **Authentication**: Supabase-based authentication with Row Level Security (RLS)
- **Rate Limiting**: Built-in rate limiting to prevent abuse
- **React UI**: Modern web interface for gem management, testing, and multimodal execution
- **Docker Ready**: Multi-stage container build installs frontend dependencies in the builder image and serves built assets from FastAPI

## 🏗️ Architecture

### System Architecture

![Architecture Diagram](https://raw.githubusercontent.com/sruckh/gemsAPI/main/docs/diagrams/architecture.svg)

gemsAPI is a full-stack application with a React frontend, FastAPI backend, Supabase database, and Google Gemini AI integration. The system supports multiple transport mechanisms including REST API, MCP SSE transport, and MCP STDIO for Claude Desktop.

**Key Components:**
- **Frontend**: React 19 + Vite with Tailwind/PostCSS build pipeline, served statically by FastAPI
- **Backend**: FastAPI with async/await, rate limiting, and CORS
- **Database**: Supabase (PostgreSQL) with Row Level Security
- **AI Integration**: Google Gemini API with text/image model routing, image attachment handling, and thinking artifact cleanup
- **MCP Server**: FastMCP integration for tool-based access

### Data Flows

![Data Flow Diagram](https://raw.githubusercontent.com/sruckh/gemsAPI/main/docs/diagrams/data-flow.svg)

**Key Workflows:**
1. **Create/Manage Gem**: User → React UI → OAuth → FastAPI → RLS Check → Supabase
2. **Execute Gem**: User → GemChat → optional image attachment / image response mode → Gemini API → cleaned text and inline image parts → chat thread
3. **MCP Integration**: MCP Client → Transport (STDIO/SSE) → FastMCP → API Auth → Database
4. **Authentication**: Google OAuth → Supabase session hydration in `AuthContext` → Bearer token → RLS Enforcement

### Database Schema

![ER Diagram](https://raw.githubusercontent.com/sruckh/gemsAPI/main/docs/diagrams/er-diagram.svg)

**Tables:**
- `auth.users` - Supabase built-in user authentication
- `public.gems` - Gem definitions with user ownership and RLS
- `public.admin_users` - Administrator accounts for full access

**Row Level Security (RLS):**
- Users can only manage their own gems
- Admin users can manage all gems
- Service role bypasses RLS for backend operations

## 🚀 Quick Start

### Prerequisites

- Docker & Docker Compose
- Supabase account and project
- Google Gemini API key

### Installation

#### 1. Clone the repository

```bash
git clone https://github.com/sruckh/gemsAPI.git
cd gemsAPI
```

#### 2. Configure environment variables

Create a `.env` file in the project root:

```bash
cp .env.example .env
```

Edit `.env` with your credentials:

```env
# Required
GEMINI_API_KEY=your_gemini_api_key
SUPABASE_URL=your_supabase_project_url
SUPABASE_KEY=your_supabase_service_role_key
VITE_SUPABASE_ANON_KEY=your_supabase_anon_key

# Optional (with defaults)
GEMINI_TEXT_MODEL=gemini-flash-latest
GEMINI_IMAGE_MODEL=gemini-3.1-flash-image
GEMINI_PRO_IMAGE_MODEL=gemini-3-pro-image
PORT=8000
NODE_ENV=production

# MCP Integration
ENABLE_MCP=true
API_TOKEN=your_secure_api_token_for_mcp
```

#### 3. Start with Docker Compose

```bash
docker compose up -d --build
```

The service will be available at `http://localhost:8000`

Notes:
- The Docker builder stage runs `npm install` inside the container image. No host-side npm install is required when you deploy with `docker compose build`.
- The frontend uses a local Tailwind/PostCSS build now; `cdn.tailwindcss.com` is no longer required at runtime.
- In Docker, `docker-compose.yml` passes `SUPABASE_URL` into the frontend build as `VITE_SUPABASE_URL`.

### Local Development (Manual)

If you prefer to run without Docker:

#### 1. Install dependencies

**Frontend:**
```bash
npm install
```

**Backend:**
```bash
pip install -r requirements.txt
```

#### 2. Run frontend (development mode)

```bash
npm run dev
```

#### 3. Run backend

```bash
uvicorn fastapi_server:app --reload --host 0.0.0.0 --port 8000
```

Notes:
- The frontend expects `VITE_SUPABASE_URL` and `VITE_SUPABASE_ANON_KEY` at build/dev time. For manual local development, define them in a Vite-readable env file such as `.env.local`.
- The backend expects `SUPABASE_URL`, `SUPABASE_KEY`, and `GEMINI_API_KEY` at runtime.
- `NODE_ENV=production` is used by the backend, but Vite may warn if that variable is present during frontend builds because it prefers controlling frontend mode itself.

## 📖 Documentation

### API Reference

#### Gems Management

| Method | Endpoint | Description |
|--------|----------|-------------|
| `GET` | `/api/gems` | List all gems (requires auth) |
| `POST` | `/api/gems` | Create a new gem (requires auth) |
| `PUT` | `/api/gems/{id}` | Update a gem (requires auth) |
| `DELETE` | `/api/gems/{id}` | Delete a gem (requires auth) |
| `GET` | `/api/gems/{id}/package` | Get gem as prompt package (requires auth) |

#### Execution

| Method | Endpoint | Description |
|--------|----------|-------------|
| `POST` | `/api/gems/execute` | Execute a gem by name |
| `POST` | `/api/gemini/generate` | Free-form generation with optional image attachments and optional image-capable responses |

#### MCP Integration

| Method | Endpoint | Description |
|--------|----------|-------------|
| `GET` | `/.well-known/mcp.json` | MCP manifest |
| `GET` | `/mcp` | MCP SSE transport endpoint |
| `GET` | `/api/mcp/ping` | MCP auth check |
| `GET` | `/api/mcp/stdio-script` | Download STDIO script for Claude Desktop |
| `GET` | `/api/mcp/claude-desktop-config` | Claude Desktop configuration |

#### Authentication

| Method | Endpoint | Description |
|--------|----------|-------------|
| `POST` | `/api/auth/check-admin` | Check if user is admin |
| `POST` | `/api/auth/register-admin` | Register first admin (one-time) |

### Configuration

| Variable | Description | Default |
|----------|-------------|---------|
| `GEMINI_API_KEY` | Google Gemini API key | *required* |
| `SUPABASE_URL` | Supabase project URL | *required* |
| `SUPABASE_KEY` | Supabase service role key | *required* |
| `VITE_SUPABASE_ANON_KEY` | Supabase anon key exposed to the frontend build | *required for web UI* |
| `GEMINI_TEXT_MODEL` | Default model for text-only chats | `gemini-flash-latest` |
| `GEMINI_IMAGE_MODEL` | Default model for image input/analysis | `gemini-3.1-flash-image` |
| `GEMINI_PRO_IMAGE_MODEL` | Default model for image generation | `gemini-3-pro-image` |
| `PORT` | Server port | `8000` |
| `NODE_ENV` | Environment mode | `production` |
| `ENABLE_MCP` | Enable MCP integration | `false` |
| `API_TOKEN` | Bearer token for API/MCP bypass | *none* |
| `FRONTEND_URL` | Allowed CORS origin when `NODE_ENV=production` | *none* |

### Database Schema

For the complete database schema with all tables, relationships, and RLS policies, see the [ER Diagram](./docs/diagrams/er-diagram.svg) above.

**Quick Reference:**
- Full SQL schema available in [`docs/supabase/gems_table.sql`](./docs/supabase/gems_table.sql)
- RLS ensures users can only access their own gems (except admins)
- Admin users table for elevated permissions

### MCP Integration

gemsAPI provides Model Context Protocol (MCP) integration for tool-based access to gems.

#### Claude Desktop Setup

1. Download the STDIO script:
```bash
curl -H "Authorization: Bearer YOUR_TOKEN" \
  https://your-domain.com/api/mcp/stdio-script \
  -o gemsapi_mcp.py
```

2. Edit your Claude Desktop config:
   - **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
   - **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`

```json
{
  "mcpServers": {
    "gemsapi": {
      "command": "python",
      "args": ["/path/to/gemsapi_mcp.py"],
      "env": {
        "GEMSAPI_TOKEN": "YOUR_SUPABASE_ACCESS_TOKEN",
        "GEMSAPI_URL": "https://your-domain.com"
      }
    }
  }
}
```

3. Install dependencies:
```bash
pip install fastmcp httpx
```

4. Restart Claude Desktop

#### Available MCP Tools

- `gems.list`: List all gems for authenticated user
- `gems.get`: Get a specific gem by ID or name
- `gems.search`: Search gems by name or description

### Web Chat Behavior

- The chat UI supports plain text prompts, image upload, and drag/drop image attachment.
- If a request includes attached input images, the backend automatically uses the configured image-capable Gemini model.
- If `Image responses` is toggled on in the UI, the backend also allows Gemini to return inline generated image parts.
- `Image responses` does not force the model to always return an image. Text-only output can still be correct for a given Gem or prompt.

### Security Considerations

**Secret hygiene:**
- Never add `SUPABASE_KEY` (service role) to `VITE_*` variables
- The backend fails to start if service key is exposed to frontend
- Use `API_TOKEN` for server-to-server communication only
- Run `npm run secret:check` before committing to scan for leaked tokens

**Authentication:**
- All data operations require valid Supabase JWT token
- Row Level Security (RLS) ensures users can only access their own gems
- Admin operations require entry in `admin_users` table
- The web UI uses Supabase OAuth and explicitly hydrates the session on load before rendering authenticated views

## 🧪 Testing

### Manual Testing

```bash
# Health check
curl http://localhost:8000/healthz

# List gems (requires auth token)
curl -H "Authorization: Bearer YOUR_TOKEN" \
  http://localhost:8000/api/gems

# Execute a gem
curl -X POST http://localhost:8000/api/gems/execute \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{"gem_name": "MyGem", "user_prompt": "Hello!"}'

# Free-form generation with image-capable response mode
curl -X POST http://localhost:8000/api/gemini/generate \
  -H "Content-Type: application/json" \
  -d '{"system_instructions":"You are helpful.","user_prompt":"Describe this image.","images":[{"data":"BASE64_BYTES","mime_type":"image/png","name":"example.png"}],"generate_images":false}'
```

### Security Scan

```bash
# Scan for leaked secrets before committing
npm run secret:check
```

## 📦 Build & Deployment

### Docker Build

```bash
# Build image
docker build -t gemsapi:latest .

# Run container
docker run -p 8000:8000 --env-file .env gemsapi:latest
```

### Production Deployment

1. Set `NODE_ENV=production` in `.env`
2. Ensure `VITE_SUPABASE_KEY` is NOT set (security check)
3. Rebuild the container image so the builder stage installs frontend deps and regenerates `dist`
4. Use reverse proxy (Nginx, Traefik) for SSL
5. Configure proper CORS origins via `FRONTEND_URL`

### Nginx Proxy Manager Example

```nginx
# Forward proxy configuration
location /gemsapi/ {
    proxy_pass http://gemsapi:8000/;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
}
```

## 🤝 Contributing

Contributions are welcome! Please follow these guidelines:

1. Fork the repository
2. Create a feature branch (`git checkout -b feature/amazing-feature`)
3. Make your changes
4. Run tests and security checks
5. Commit changes (`git commit -m 'Add amazing feature'`)
6. Push to branch (`git push origin feature/amazing-feature`)
7. Open a Pull Request

### Development Guidelines

- Follow existing code style and patterns
- Add TypeScript types for all new code
- Update documentation for API changes
- Test MCP integration when modifying tools
- Rebuild the container after frontend dependency changes so the builder stage picks them up
- Run `npm run secret:check` before committing

## 📄 License

This project is licensed under the MIT License - see [LICENSE](LICENSE) for details.

## 🙏 Acknowledgments

- **Google** - For the Gemini AI models and API
- **Supabase** - For the excellent PostgreSQL backend service
- **FastAPI** - For the modern Python web framework
- **React** - For the frontend UI framework
- **FastMCP** - For MCP integration toolkit

## 📚 Additional Documentation

- [Phase 2 MCP Integration](./phase-2-MCP.md) - MCP implementation details
- [CLAUDE.md](./CLAUDE.md) - Project-specific guidance for Claude Code
- [AGENTS.md](./AGENTS.md) - Agent configuration and usage

## 🔗 Links

- [Gemini API Documentation](https://ai.google.dev/)
- [Supabase Documentation](https://supabase.com/docs)
- [FastAPI Documentation](https://fastapi.tiangolo.com/)
- [MCP Specification](https://modelcontextprotocol.io/)

gemsAPI

gemsAPI 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

gemsAPI

gemsAPI 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README