API Platform Conference 2026

Plug the conference
into your AI agent

Ask about the agenda, the 28 speakers and the partners — or build your own assistant on top of the API Platform Conference 2026 (17–18 September, Lille).

MCP server · live

Endpoint

http://mcp.con.api-platform.com/mcp

Streamable HTTP transport (MCP spec 2025-06-18). Read tools need no auth. Voting, commenting and personal agenda require a GitHub token (see below).

Install on your client

Claude Code (CLI)

claude mcp add --transport http apiplatformcon http://mcp.con.api-platform.com/mcp

Gemini CLI

gemini mcp add --transport http apiplatformcon http://mcp.con.api-platform.com/mcp

Cursor & VS Code (native HTTP MCP)

Add to ~/.cursor/mcp.json or .vscode/mcp.json:

{
  "mcpServers": {
    "apiplatformcon": {
      "type": "http",
      "url": "http://mcp.con.api-platform.com/mcp"
    }
  }
}

Claude Desktop & other stdio-only clients

Bridge the remote server through mcp-remote in your config file:

{
  "mcpServers": {
    "apiplatformcon": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "http://mcp.con.api-platform.com/mcp"]
    }
  }
}

ChatGPT

Settings → Connectors → Add custom connector → paste the endpoint URL above.

Voting, commenting & personal agenda (GitHub login)

The read tools are open. vote-talk, comment-talk, attend-talk, unattend-talk, my-agenda, clear-agenda and become-partner are attributed to your GitHub account, so they need a token. Create a personal access token (the read:user scope is enough — no repo access) and send it as a Bearer token. One vote per talk per user; re-voting updates your rating. Attendance is idempotent.

Claude Code (CLI)

claude mcp add --transport http \
  --header "Authorization: Bearer $GITHUB_TOKEN" \
  apiplatformcon http://mcp.con.api-platform.com/mcp

Cursor / VS Code / native HTTP

{
  "mcpServers": {
    "apiplatformcon": {
      "type": "http",
      "url": "http://mcp.con.api-platform.com/mcp",
      "headers": { "Authorization": "Bearer <your-github-token>" }
    }
  }
}

The server validates the token against the GitHub user API; the token itself is never stored. Only your GitHub id and login are saved with your vote/comment/attendance.

20 tools

event-infodates, venue, tracks, tickets
list-talksfilter by room/type/speaker/day
get-talkone talk by slug/keywords
search-talksfull-text talk search
current-talksessions in progress now
next-talksnext upcoming slots
list-categoriesall talk categories
list-hotelspartner hotels · 10% code
list-speakersfilter by search
get-speakerone speaker + their talks
speaker-historypast editions + replay links
list-partnerssponsors by tier
become-partnersponsorship levels · GitHub login
talk-feedbackread votes + comments
vote-talkrate a talk · GitHub login
comment-talkcomment · GitHub login
attend-talksave talk to agenda
unattend-talkremove from agenda
clear-agendaremove every saved talk
my-agendalist your saved talks