Connect SofiaStage Events and your agent gets 5 tools, among them get_editorial, get_event, get_performer. It answers at https://api.sofiastage.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Read-only tools for current SofiaStage events, venues, cities, performers, and editorial.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_editorial | Get a SofiaStage editorial collection, article metadata, and precomputed upcoming events by exact title or route slug. Inputs: name_or_slug |
get_event | Get one event by canonical show_stable_id or legacy source ID, optionally including related performers and editorial entries. Inputs: event_id, include |
get_performer | Get a SofiaStage performer or creative-team profile, biography metadata, public links, and precomputed upcoming events by exact name or route slug. Inputs: name_or_slug |
search_catalog | Search cities, venues, production titles, performers, or editorial collections. Performer and editorial results are compact; use their detail tools next. Inputs: kind, query, scope, city, limit |
search_events | Search current cultural events by Sofia/all-city scope, city, date, local time, venue, title, performer, or editorial collection. Returns stable event IDs and cursor pagination. Inputs: query, scope, city, date_from, date_to, relative_date |
Every block below points at https://api.sofiastage.com/mcp. Pick your client and copy.
claude mcp add --transport http sofiastage-events https://api.sofiastage.com/mcp
{
"mcpServers": {
"sofiastage-events": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.sofiastage.com/mcp"]
}
}
}{
"mcpServers": {
"sofiastage-events": {
"url": "https://api.sofiastage.com/mcp"
}
}
}{
"servers": {
"sofiastage-events": {
"type": "http",
"url": "https://api.sofiastage.com/mcp"
}
}
}{
"context_servers": {
"sofiastage-events": {
"url": "https://api.sofiastage.com/mcp"
}
}
}{
"mcpServers": {
"sofiastage-events": {
"serverUrl": "https://api.sofiastage.com/mcp"
}
}
}{
"mcpServers": {
"sofiastage-events": {
"url": "https://api.sofiastage.com/mcp"
}
}
}name: SofiaStage Events
version: 0.0.1
schema: v1
mcpServers:
- name: SofiaStage Events
type: streamable-http
url: https://api.sofiastage.com/mcp{
"mcpServers": {
"sofiastage-events": {
"httpUrl": "https://api.sofiastage.com/mcp"
}
}
}{
"mcpServers": {
"sofiastage-events": {
"type": "http",
"url": "https://api.sofiastage.com/mcp"
}
}
}{
"mcpServers": {
"sofiastage-events": {
"url": "https://api.sofiastage.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.sofiastage.com%2Fmcp&type=streamable_http&id=sofiastage-events&name=SofiaStage%20Events
It answered our last check on 19 October 2026 in 329 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by sofiastage.com and served from api.sofiastage.com, the vendor's own domain: https://api.sofiastage.com/mcp.
5, as returned by the server's own tools/list on 11 September 2026: get_editorial, get_event, get_performer, search_catalog, search_events.
It answered our last check on 19 October 2026 in 329 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.sofiastage.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.sofiastage. Endpoint host: api.sofiastage.com. ARD identifier: urn:air:com.sofiastage:mcp:events.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.