mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_connect_calendar / alternatives

Live alternatives to mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_connect_calendar

The best live alternatives to mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_connect_calendar right now are mcp-registry/io.github.bdentech/chieflab/chieflab_connect_provider, mcp-registry/io.corpusiq/multi-source-mcp/calendar_connector, mcp-registry/io.github.marian-kamenistak/elc-conference-mcp-tickets/add-to-calendar, mcp-registry/io.github.dynamitecircle/dc/calendar, mcp-registry/dev.metamesh-uga/metamesh-uga/google-calendar — capability-matched and ranked by current reliability. mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_connect_calendar itself is currently "healthy".

alternative	server
mcp-registry/io.github.bdentech/chieflab/chieflab_connect_provider	io.github.bdentech/chieflab	live status →
mcp-registry/io.corpusiq/multi-source-mcp/calendar_connector	io.corpusiq/multi-source-mcp	live status →
mcp-registry/io.github.marian-kamenistak/elc-conference-mcp-tickets/add-to-calendar	io.github.marian-kamenistak/elc-conference-mcp-tickets	live status →
mcp-registry/io.github.dynamitecircle/dc/calendar	io.github.dynamitecircle/dc	live status →
mcp-registry/dev.metamesh-uga/metamesh-uga/google-calendar	dev.metamesh-uga/metamesh-uga	live status →
mcp-registry/io.github.gomission/mcp/mission_start_connector_setup	io.github.gomission/mcp	live status →
mcp-registry/io.corpusiq/multi-source-mcp/calendly_connector	io.corpusiq/multi-source-mcp	live status →
mcp-registry/me.whenmeet/scheduler/create_meeting	me.whenmeet/scheduler	live status →
mcp-registry/io.github.pipeworx-io/calendly/current_user	io.github.pipeworx-io/calendly	live status →

FAQ

What is the best alternative to mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_connect_calendar?

mcp-registry/io.github.bdentech/chieflab/chieflab_connect_provider is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.corpusiq/multi-source-mcp/calendar_connector, mcp-registry/io.github.marian-kamenistak/elc-conference-mcp-tickets/add-to-calendar, mcp-registry/io.github.dynamitecircle/dc/calendar, mcp-registry/dev.metamesh-uga/metamesh-uga/google-calendar. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_connect_calendar down right now?

mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_connect_calendar's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.luisa-sys%2Flyra-mcp-server%2Flyra_connect_calendar.

How does Glimind pick alternatives?

By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.luisa-sys%2Flyra-mcp-server%2Flyra_connect_calendar or MCP find_alternatives. Check mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_connect_calendar's live status: https://glimind.com/tool/mcp-registry/io.github.luisa-sys/lyra-mcp-server/lyra_connect_calendar.