MCP integration

Use the RigaTech ecosystem from inside your IDE or chat tool. We host an MCP server that exposes events, jobs, courses and resources as MCP tools, so Claude Desktop, Cursor, Continue and any MCP-compatible client can query them directly.

> Tools the server exposes

list_events()Upcoming meetups, conferences, hackathons.
list_jobs()Open positions, filterable by stack and seniority.
list_courses()Cohort and self-paced programs.
list_resources()Accelerators, VCs, coworking, communities, media.
search()Fuzzy search across every entity.

> Endpoint

Hosted at

https://mcp.riga.tech

live

> Quick install

The `mcp-remote` bridge drops the hosted server into any stdio-based MCP client. No auth, read-only, no install on our side.

$ npx -y mcp-remote https://mcp.riga.tech

> Add to your client

Drop this snippet into your client's MCP config. Same JSON works in every stdio client thanks to the mcp-remote bridge.

Claude Desktop

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

{
  "mcpServers": {
    "rigatech": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.riga.tech"]
    }
  }
}

Cursor

~/.cursor/mcp.json

{
  "mcpServers": {
    "rigatech": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.riga.tech"]
    }
  }
}

VS Code · Continue

.continue/config.json in your repo or home

{
  "mcpServers": {
    "rigatech": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.riga.tech"]
    }
  }
}

Native HTTP / SSE clients

Clients with built-in HTTP transport (recent Cursor builds, VS Code 1.96+) can talk to the endpoint directly without the bridge.

{
  "mcpServers": {
    "rigatech": { "url": "https://mcp.riga.tech" }
  }
}

> How it works

The server reads the same rigatech-data GitHub repo that backs this site, validated through the same Zod schemas. Read-only: it never writes. Updates are live as soon as a PR merges.

Open endpoint (mcp.riga.tech)