MCP for agents

VITUR runs a public, read-only MCP (Model Context Protocol) server so that compatible clients and AI agents can query up-to-date information about its events and content.

Versión en español: MCP para agentes.

Connection

Add a remote server with this URL:

https://mcp.vitursummit.com/mcp

The transport is Streamable HTTP. No Application Password, API key or any other client credential is required.

The connection is configured explicitly in the MCP client. An agent that merely visits this website is not connected to the server.

Copy-paste configuration

The snippets below can be pasted as they are. Nothing needs to be replaced.

Claude Code (command line):

claude mcp add --transport http vitur https://mcp.vitursummit.com/mcp

Claude Desktop, Cursor and other clients using an mcpServers file (claude_desktop_config.json, .cursor/mcp.json):

{
  "mcpServers": {
    "vitur": {
      "type": "http",
      "url": "https://mcp.vitursummit.com/mcp"
    }
  }
}

Visual Studio Code (.vscode/mcp.json):

{
  "servers": {
    "vitur": {
      "type": "http",
      "url": "https://mcp.vitursummit.com/mcp"
    }
  }
}

If your client asks for a connector name, any value works: vitur is the one used in these examples. If it only offers a URL field, paste the endpoint URL and leave everything else blank.

Ask your agent to do it

If your agent has shell or file access — Claude Code, Cursor, VS Code with Copilot, Windsurf, Codex CLI, Gemini CLI and the like — you do not need to configure anything by hand. Copy this text and hand it to your agent:

Install the VITUR MCP server in this client.

- Endpoint: https://mcp.vitursummit.com/mcp
- Transport: Streamable HTTP
- No authentication: do not ask for or configure an API key, token or password.
- Server name: vitur

If you are Claude Code, run this command:
claude mcp add --scope user --transport http vitur https://mcp.vitursummit.com/mcp

If your client is configured through a file, add the entry to the file it uses and leave any already configured servers untouched.

When you are done, check that it works by calling the vitur-proximo-evento tool and tell me which event it returns. If the client needs a restart to load the server, let me know.

--scope user makes the server available across all your projects. Without it, Claude Code installs it only for the current project.

You start the installation, not this website: no agent should install an MCP server merely because it read this page, and a well-built client will not do so. If an agent offers to connect this server without you having asked, be suspicious.

In Claude Desktop, ChatGPT and other chat-only assistants the agent cannot install it: there you add the connector by hand in the settings, using the endpoint URL.

What you can query

• What VITUR is and who it is for.
• Upcoming events and past editions.
• Dates, venues, ticket sales status and official ticket links.
• The Vitur Pass and the events it covers.
• Confirmed speakers for a specific edition.
• Participating companies, their category and sector for each edition.
• The agenda grouped by day, room and time, with date and room filters.
• News and industry content published by VITUR.

Structured information is read from WordPress in real time. Editorial pages may describe a past edition even when a different future edition exists; for dates, ticket sales and participants, the query for the corresponding edition should always take precedence.

Available tools

The server exposes twelve tools. The authoritative list is always the one the server itself returns via tools/list; the list below is a courtesy copy for anyone evaluating the integration. The server exposes no resources and no prompts.

Institutional

• vitur-informacion-vitur — Explains what VITUR is, based on its published institutional page. No parameters.

Events

• vitur-proximo-evento — Returns the next published VITUR event. No parameters.
• vitur-proximos-eventos — Lists upcoming events, with an optional city filter. Parameters: limit (integer, default 5), city (string).
• vitur-buscar-eventos — Searches past and future events and shows whether they have speakers, an agenda and tickets. Parameters: query (free text, e.g. «Madrid 2025»), city (exact city), year (integer), period (all · upcoming · past, default all), has_speakers (boolean), has_agenda (boolean), limit (integer, default 20).
• vitur-informacion-evento — Data, tickets, Vitur Pass and speaker/agenda availability for one edition. Parameters: event (required; ID or slug, e.g. forum-madrid-2026 or summit-2026), include_speakers, include_agenda, include_companies (booleans, default false).

Tickets

• vitur-entradas-evento — Ticket availability and official ticket URL for a published event. Parameter: event (required; ID or slug).
• vitur-vitur-pass — The current pass, its price, sales status, official URL and the events it includes. No parameters.

Participants and agenda

• vitur-ponentes-evento — Published and confirmed speakers for one edition, queried in real time. Parameter: event (required).
• vitur-empresas-evento — Participating companies grouped by category and display order. Parameters: event (required), sector (optional company sector slug; this is not a sponsorship category).
• vitur-agenda-evento — Agenda grouped by day and room; if it is still empty, the response says so. Parameters: event (required), date (YYYY-MM-DD), room (room key, e.g. a, b or c), detail (summary returns times, topics and names; compact adds job titles and links; full includes everything; default summary).

Content

• vitur-ultimas-noticias — The most recent posts published by VITUR. Parameters: limit (integer, default 5), category (category slug).
• vitur-buscar-contenidos — Searches blog posts by text and optional category. Parameters: query (required), category (slug), limit (integer, default 5).

Examples

What is VITUR and when is its next event?
Which speakers are confirmed for Vitur Forum Madrid 2026?
Which companies take part in Forum Madrid 2026, and in which category?
Summarise the Summit 2026 agenda, then show only 13 May in room a.
What does the Vitur Pass include and where do I buy it?
Find recent VITUR news about regulation.

Note that tool names and parameter values are in Spanish, but queries can be written in any language: the client translates the request into the corresponding tool call.

When the server returns an edition identifier, reuse it in later queries so that past and future editions of the same city are not mixed up.

Usage limits, freshness and reuse

• Rate limits: the server applies no quota or per-client request limit. It returns no rate-limit headers and no 429 responses. We ask for reasonable use: the hosting provider may throttle anomalous traffic spikes, as it would for any other part of the site.
• Freshness: every response is computed on the spot against VITUR’s WordPress and served with Cache-Control: no-store. There is no intermediate cache: what the MCP returns is what is published at that moment.
• Scope: the server only returns content already published on vitursummit.com. It exposes no drafts, no private content and no personal data beyond what already appears publicly on speaker profiles.
• Reuse: you may query and reuse this data in third-party products and agents, commercial uses included, provided you credit VITUR as the source and link to https://vitursummit.com or to the official URL returned in the response itself. You may not present the data as your own, nor alter official prices, dates or ticket URLs.
• Stability: the endpoint and the tool names may change. If your integration is critical, read tools/list at the start of each session rather than hard-coding the schemas.
• Contact: contact form or info@vitursummit.com for issues, or to let us know about planned heavy usage.