convez.ai
MCP ServerIntegração & APIsAvançado
kpjmd

SidelineIQ MCP Servers

kpjmd/sidelineiq-mcp-servers

Servidores MCP para plataforma autônoma de inteligência de lesões esportivas

Ver no GitHub
InicialPluginScore · de 0 a 100

Suite de servidores MCP (Model Context Protocol) para a plataforma SidelineIQ de inteligência de lesões esportivas. Fornece integração com Farcaster, Twitter/X e banco de dados PostgreSQL para publicação autônoma e gerenciamento de posts sobre lesões esportivas via agentes Claude.

Instalação

$npx convez-ai kpjmd/sidelineiq-mcp-servers

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 2 semanas
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Publicação autônoma de análises de lesões em Farcaster e Twitter
  • Gerenciamento centralizado de posts sobre lesões esportivas
  • Integração de agentes Claude com APIs de redes sociais e banco de dados

Veredito

Implementação robusta de MCP servers em TypeScript com arquitetura modular e multi-transporte para caso de uso específico de sports intelligence. Bem estruturado mas requer configuração complexa de credenciais externas (Neynar, Twitter API, PostgreSQL).

README

A tradução para o português deste README ainda está na fila.

SidelineIQ MCP Servers

MCP (Model Context Protocol) server suite for SidelineIQ — an autonomous AI sports injury intelligence platform. This repository houses all MCP servers that the SidelineIQ Injury Intelligence Agent uses as tools.

Architecture

┌─────────────────────┐     HTTP      ┌──────────────────────────────┐
│  sidelineiq-agents  │ ────────────> │  sidelineiq-mcp-servers      │
│  (Claude Agent)     │               │                              │
└─────────────────────┘               │  ┌─ Farcaster Server :3101   │
                                      │  ├─ Twitter Server   :3102   │
                                      │  └─ Web Server       :3103   │
                                      └──────────────────────────────┘
                                               │            │
                                               ▼            ▼
                                         External APIs   Neon PostgreSQL

Each server is an independent Express app exposing MCP tools via Streamable HTTP transport on /mcp. All servers are stateless and deployed as separate Railway processes.

Servers & Tools

Farcaster MCP Server (port 3101)

Publishes to Farcaster via Neynar API.

ToolDescription
farcaster_publish_castPublish a single cast (max 320 chars)
farcaster_publish_threadPublish a multi-cast thread (2-10 casts)
farcaster_get_castRetrieve a cast by hash
farcaster_delete_castDelete a cast by hash

Twitter MCP Server (port 3102)

Publishes to X/Twitter via Twitter API v2.

ToolDescription
twitter_publish_tweetPublish a single tweet (max 280 chars)
twitter_publish_threadPublish a multi-tweet thread (2-10 tweets)
twitter_get_tweetRetrieve a tweet by ID
twitter_delete_tweetDelete a tweet by ID

SidelineIQ Web MCP Server (port 3103)

Reads/writes injury posts to Neon PostgreSQL.

ToolDescription
web_create_injury_postCreate a new injury post
web_update_injury_postUpdate an existing post
web_get_postRetrieve a post by ID
web_flag_for_md_reviewFlag a post for MD review
web_list_postsList/filter injury posts

Quick Start

Prerequisites

  • Node.js 18+
  • Neon PostgreSQL database
  • Neynar API key (for Farcaster)
  • Twitter API v2 credentials (for Twitter)

Setup

# Clone and install
git clone <repo-url>
cd sidelineiq-mcp-servers
npm install

# Configure environment
cp .env.example .env
# Fill in your API keys in .env

# Run database migration
psql $DATABASE_URL -f src/shared/migrations/001_injury_posts.sql

# Start all servers (development)
npm run dev

# Or start individual servers
npm run dev:farcaster
npm run dev:twitter
npm run dev:web

Verify

Each server exposes a health endpoint:

curl http://localhost:3101/health  # Farcaster
curl http://localhost:3102/health  # Twitter
curl http://localhost:3103/health  # Web

Environment Variables

See .env.example for all required variables:

VariableDescription
PORT_FARCASTERFarcaster server port (default: 3101)
PORT_TWITTERTwitter server port (default: 3102)
PORT_WEBWeb server port (default: 3103)
NEYNAR_API_KEYNeynar API key for Farcaster
NEYNAR_SIGNER_UUIDNeynar signer UUID
SIDELINEIQ_FARCASTER_FIDSidelineIQ Farcaster FID
TWITTER_API_KEYTwitter API key
TWITTER_API_SECRETTwitter API secret
TWITTER_ACCESS_TOKENTwitter access token
TWITTER_ACCESS_TOKEN_SECRETTwitter access token secret
TWITTER_BEARER_TOKENTwitter bearer token
DATABASE_URLNeon PostgreSQL connection string
MD_REVIEW_CONFIDENCE_THRESHOLDConfidence threshold for MD review (default: 0.75)

Development

# Build
npm run build

# Type check
npm run lint

# Run tests
npm test

# Watch tests
npm run test:watch

Railway Deployment

Each server deploys as a separate Railway process via the Procfile:

farcaster: node dist/servers/farcaster/server.js
twitter: node dist/servers/twitter/server.js
web: node dist/servers/web/server.js
  1. Connect the repo to Railway
  2. Set all environment variables in Railway dashboard
  3. Railway auto-detects the Procfile and runs each process

Each server is independently restartable.

Adding a New MCP Server

  1. Create src/servers/{name}/ directory
  2. Add server.ts (Express + MCP server setup)
  3. Add client.ts (API client wrapper)
  4. Add tools.ts (tool definitions with Zod schemas)
  5. Add port assignment to CLAUDE.md and .env.example
  6. Register in src/index.ts
  7. Add Railway process to Procfile
  8. Add tests in tests/{name}.test.ts
  9. Update this README

Tool Naming Convention

Format: {server}_{action}_{resource}

  • Always snake_case
  • Always service-prefixed
  • Examples: farcaster_publish_cast, twitter_delete_tweet, web_create_injury_post

Project Structure

src/
├── index.ts                    # Main entry (starts all servers)
├── shared/
│   ├── database.ts             # Neon PostgreSQL client
│   ├── errors.ts               # Error handling utilities
│   ├── logger.ts               # Structured logging (stderr only)
│   ├── types.ts                # Shared TypeScript interfaces
│   └── migrations/
│       └── 001_injury_posts.sql
└── servers/
    ├── farcaster/
    │   ├── server.ts
    │   ├── client.ts
    │   └── tools.ts
    ├── twitter/
    │   ├── server.ts
    │   ├── client.ts
    │   └── tools.ts
    └── web/
        ├── server.ts
        ├── client.ts
        └── tools.ts

Related Repositories

  • sidelineiq-agents — Consumes these MCP servers as tools via HTTP
  • sidelineiq — Frontend (Next.js/Vercel), reads from the same Neon database
  • orthoiq-agents — Separate platform, independent codebase
Ver o original no GitHub

Bom para

Relacionados