INDIVIDUAL MCP TOOL
get_event_details
Get the details of The Physical AI Sprint: the date, start and end times, hosting organizations, the three project tracks, the robot hardware available, the judging criteria, the submission deadline, and how to register.
LIVE ENDPOINT
https://www.buildspace.tv/api/mcp
Connect to this endpoint to inspect the live schema for get_event_details and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.physical-ai-sprint]
url = "https://www.buildspace.tv/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"physical-ai-sprint": {
"type": "http",
"url": "https://www.buildspace.tv/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: physical-ai-sprint
Remote MCP URL: https://www.buildspace.tv/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"physical-ai-sprint": {
"url": "https://www.buildspace.tv/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"physical-ai-sprint": {
"type": "http",
"url": "https://www.buildspace.tv/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "physical-ai-sprint",
"transport": "streamable-http",
"url": "https://www.buildspace.tv/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
list_teams— List the teams taking part in The Physical AI Sprint, with each team's roster, the skills they already have, and the skills they are still looking for.get_team— Get a single hackathon team by its slug, including the full roster with GitHub handles, the pitch describing what they want to build, and the URL of the GitHub thread where people ask to join.list_projects— List the projects submitted to the showcase, with the track each ran in (simulation only, hardware only, or both), the robots used, demo media, and the team that built it.search_hackathon— Search across everything at once: team names and pitches, the skills teams are seeking, project titles and descriptions, the robots used, and people by name or GitHub handle.