Event Network

Search the public Event Network directory for companies, specialists, Cross Rental and used-equipment offers, jobs and briefs, venues and rooms.

Fifteen read-only tools provide public search filters, profile and listing details, technical plans, filter dictionaries, and shared date-specific availability when the source makes it available. Results are paginated (default 20, maximum 50).

MCP connector

Server URL: https://mcp.eventnetwork.eu/mcp
Login: None
Protocol: MCP 2026-07-28
Instructions: All tools are read-only. Public search never uses account credentials. Account tools require New Systems OAuth; use first. If several profiles fit, ask which to use. Every private call must name its context, and answers must identify it. Never change the active profile on the site or in another conversation. Before , inspect the selected item and require capabilities.calendar=true. If no selected context supports a calendar, report unknown because availability cannot be confirmed; do not call the tool or turn that limitation into an API error. If called, report status and statusSummary first, and never expose calendar event details. Use before using IDs or specialization keys. Do not invent specialization keys from labels. Synonyms and translated labels in the directory are searchable. For nearby searches use nearCity, radiusKm and country; distances are straight-line, never road distances. Do not silently widen filters or automatically paginate the whole directory. Every search response reports appliedFilters. If an exact-city search returns no results, suggestedNextSearch is only a proposal; ask the user before making that broader search. When minCapacity is requested for a venue, ask which room layout is required. A needs_clarification response must be passed to the user before retrying. Never sum rooms or equate bedrooms with beds. For room availability, find a public venue and inspect its profile first. If roomCount is zero or rooms is empty, no room was checked: continue with another venue from the search results, following nextPage only as needed, and do not report calendar status for that venue. Call only with an active room returned by . If no active room can be found, say that availability could not be checked because there is no eligible room; do not label that as calendar status unknown. Report profileType, ownedEquipment and supportedEquipment distinctly: ownership is not operating proficiency. Calendar sharing does not prove availability; ask for exact dates before checking. Use IDs returned by search tools when fetching a company or specialist profile. Follow nextPage when more search results are needed. For company searches, verify rental claims from the returned public company type, specializations, or profile text. A keyword match alone is not proof that a company offers rental. For specialist searches, skills are public certificates/skills and equipment is only equipment listed on the profile; listed equipment does not prove operating proficiency. Do not claim a specialist can operate a console or software unless the returned data explicitly supports that claim. For availability, search candidates first and call with each specialistId, the exact inclusive date range, and an IANA timezone. Report the returned status and its statusSummary; do not answer with only the specialist ID. Report available only for status available; busy means busy; unknown means availability cannot be confirmed and must not be treated as free. Never reveal calendar event details. A specialist city filter matches the city stored on the profile. worksInCountries indicates country-level work coverage. Availability checks do not verify that a specialist can work at a particular city or venue; disclose that limit when relevant. For equipment searches, query is model text only. When the user gives both a manufacturer and model, pass them separately as manufacturer and model; do not combine them into query. Empty optional filters mean no filter. Report quantityTotal as the listing’s published total and availabilitySharingEnabled as the company’s explicit availability-sharing setting. For date-specific counts, pass dateFrom and optionally dateTo plus an IANA timezone. Report quantityAvailable only when availabilityStatus is available or unavailable; unknown means the shared inventory did not provide a confirmed count. Never infer availability from a company calendar status or expose booking details. Use for active public second-hand/used-equipment sale listings. This is separate from , which searches Cross Rental rental listings. Do not expose seller personal contact details or infer quantities or date-specific availability. Use for public venues. Match venue types by their public name, use minStars for minimum stars and minCapacity with an explicit roomLayout for the capacity of one active room. Never add capacities across rooms. Use nearCity for a geographic search; Warsaw means Warszawa, country PL, and the default radius is 50 km. Do not return exact street addresses or coordinates. If a requested date has no year and cannot be safely resolved from context, ask for the year. Do not silently reinterpret a date that has already passed. For every company, specialist (including speakers and artists), or equipment owner result whose schema provides confirmedCollaborationsCount, include the value alongside the name and profile link. A numeric zero is a confirmed zero; null means the platform did not provide a count. Never infer or calculate this count. Respond in the user’s language, include a clickable Markdown link from profileUrl for each company, specialist (including speakers and artists), venue, job, rental listing, used-equipment result, purchase group, and rider you present, and clearly label missing or unknown information. Do not invent directory results.

Tools

Reads data23

Skills

None in the store listings or on the server

MCP connector

Server URL

https://mcp.eventnetwork.eu/mcp

None

Protocol

MCP 2026-07-28

Instructions

All tools are read-only. Public search never uses account credentials. Account tools require New Systems OAuth; use first. If several profiles fit, ask which to use. Every private call must name its context, and answers must identify it. Never change the active profile on the site or in another conversation. Before , inspect the selected item and require capabilities.calendar=true. If no selected context supports a calendar, report unknown because availability cannot be confirmed; do not call the tool or turn that limitation into an API error. If called, report status and statusSummary first, and never expose calendar event details. Use before using IDs or specialization keys. Do not invent specialization keys from labels. Synonyms and translated labels in the directory are searchable. For nearby searches use nearCity, radiusKm and country; distances are straight-line, never road distances. Do not silently widen filters or automatically paginate the whole directory. Every search response reports appliedFilters. If an exact-city search returns no results, suggestedNextSearch is only a proposal; ask the user before making that broader search. When minCapacity is requested for a venue, ask which room layout is required. A needs_clarification response must be passed to the user before retrying. Never sum rooms or equate bedrooms with beds. For room availability, find a public venue and inspect its profile first. If roomCount is zero or rooms is empty, no room was checked: continue with another venue from the search results, following nextPage only as needed, and do not report calendar status for that venue. Call only with an active room returned by . If no active room can be found, say that availability could not be checked because there is no eligible room; do not label that as calendar status unknown. Report profileType, ownedEquipment and supportedEquipment distinctly: ownership is not operating proficiency. Calendar sharing does not prove availability; ask for exact dates before checking. Use IDs returned by search tools when fetching a company or specialist profile. Follow nextPage when more search results are needed. For company searches, verify rental claims from the returned public company type, specializations, or profile text. A keyword match alone is not proof that a company offers rental. For specialist searches, skills are public certificates/skills and equipment is only equipment listed on the profile; listed equipment does not prove operating proficiency. Do not claim a specialist can operate a console or software unless the returned data explicitly supports that claim. For availability, search candidates first and call with each specialistId, the exact inclusive date range, and an IANA timezone. Report the returned status and its statusSummary; do not answer with only the specialist ID. Report available only for status available; busy means busy; unknown means availability cannot be confirmed and must not be treated as free. Never reveal calendar event details. A specialist city filter matches the city stored on the profile. worksInCountries indicates country-level work coverage. Availability checks do not verify that a specialist can work at a particular city or venue; disclose that limit when relevant. For equipment searches, query is model text only. When the user gives both a manufacturer and model, pass them separately as manufacturer and model; do not combine them into query. Empty optional filters mean no filter. Report quantityTotal as the listing’s published total and availabilitySharingEnabled as the company’s explicit availability-sharing setting. For date-specific counts, pass dateFrom and optionally dateTo plus an IANA timezone. Report quantityAvailable only when availabilityStatus is available or unavailable; unknown means the shared inventory did not provide a confirmed count. Never infer availability from a company calendar status or expose booking details. Use for active public second-hand/used-equipment sale listings. This is separate from , which searches Cross Rental rental listings. Do not expose seller personal contact details or infer quantities or date-specific availability. Use for public venues. Match venue types by their public name, use minStars for minimum stars and minCapacity with an explicit roomLayout for the capacity of one active room. Never add capacities across rooms. Use nearCity for a geographic search; Warsaw means Warszawa, country PL, and the default radius is 50 km. Do not return exact street addresses or coordinates. If a requested date has no year and cannot be safely resolved from context, ask for the year. Do not silently reinterpret a date that has already passed. For every company, specialist (including speakers and artists), or equipment owner result whose schema provides confirmedCollaborationsCount, include the value alongside the name and profile link. A numeric zero is a confirmed zero; null means the platform did not provide a count. Never infer or calculate this count. Respond in the user’s language, include a clickable Markdown link from profileUrl for each company, specialist (including speakers and artists), venue, job, rental listing, used-equipment result, purchase group, and rider you present, and clearly label missing or unknown information. Do not invent directory results.

Tools