vex

This MCP server provides access to VEX Robotics Competition data via the RobotEvents API. It exposes a set of MCP tools such as search-teams, get-team-info, search-events, get-event-details, get-team-rankings, get-skills-scores, and forum-related tools to Claude Desktop or other MCP clients. With the vex server, you can query teams, events, rankings, and skills scores, as well as explore forum topics and posts, enabling comprehensive competition data retrieval in a standard MCP format. Configure Claude Desktop to point at this server so you can ask natural language questions like finding teams by location, retrieving event details, or analyzing a team’s performance history. The server supports both production usage using the public RobotEvents data and development setup for local testing.

Prerequisites:

• Node.js 18.0.0 or higher
• npm (comes with Node.js)
• A RobotEvents API token (JWT) with appropriate permissions

Method 1: NPM Installation (Recommended)

One-line installation:

npm install -g vex-mcp-server

Get your RobotEvents API token:

1. Visit https://www.robotevents.com/api/v2
2. Click "Request API Access" and fill out the form
3. Once approved, copy your JWT token

That token should be placed in your MCP client configuration (see mcp_config). You can now run vex-mcp-server directly.

Method 2: Development Installation

For developers who want to modify the code:

git clone https://github.com/yangjack8192/vex-mcp-server.git
cd vex-mcp-server
npm install
npm run build

Run locally (development):

npm start

Note: In development, point your MCP client to the built index, typically via a node command as shown in the repository examples.

Tips and considerations:

• Set ROBOTEVENTS_TOKEN in your MCP client or environment to authorize RobotEvents API requests.
• In Claude Desktop, configure the mcpServers entry for vex with command vex-mcp-server and include ROBOTEVENTS_TOKEN in env as shown.
• Restart Claude Desktop after updating the configuration.
• If you switch between npm installation and development builds, ensure the appropriate path or command is used in your configuration.
• The server exposes many tools; reference the API Tools Reference in the README to construct queries like search-teams, get-event-details, and analyze-match-opponents.
• Ensure you have network access to RobotEvents API endpoints and that your token has the necessary scopes.