Skip to main content
Glama
midnight480

saga-event-space-mcp-server

by midnight480
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to saga-event-space-mcp-server

No user-submitted related servers found.

    Related Servers

    • jp-data-mcp

      kimotostudio
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Japanese public business data, enabling AI agents to validate and look up corporate numbers, search bank/branch codes, and check national holidays. Runs locally with no telemetry; live corporate registry data requires a free NTA app ID.
      8
      MIT

    • chouseisan-mcp

      soyalumno
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server to read and write events on chouseisan.com (Chouseisan), a Japanese scheduling tool, using unofficial HTTP protocol. Enables creating events, fetching schedules, and managing responses via AI agents or CLI.
      -
    • kintone MCP Server by kintone

      kintone MCP Serverofficial

      kintone
      A
      license
      A
      quality
      A
      maintenance
      Official MCP server for kintone, enabling AI assistants to manage kintone apps, records, and settings through natural language.
      20
      711 npm
      56
      Apache 2.0

    • hailab-japan-company-data

      HOTAgithub
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server to search Japanese companies by corporate number or name and retrieve financial, subsidy, and procurement information from gBizINFO public data. Enables AI agents to query Japanese company data through natural language.
      -

    • kanpou-mcp

      yoshinaga2015
      F
      license
      B
      quality
      D
      maintenance
      MCP server for searching Japanese government procurement notices via the Kanpou API. Enables LLMs to search by date, keyword, or detailed criteria.
      3
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 36 tools

    Disambiguation4/5

    Most tools clearly combine a resource with an action, so places, announcements, release notes, tokens, users, audit logs, deletion requests, and duplicates are generally easy to tell apart. A few workflow-adjacent pairs (approve_deletion_request vs delete_place, resolve_duplicate vs merge_duplicate, update_place vs bulk_update_status) share boundary behavior and could cause an agent to pick the wrong one without careful reading.

    Naming Consistency4/5

    Tool names almost universally follow a snake_case verb_noun pattern (create_place, update_announcement, delete_token), and list/get usage is mostly consistent. Minor deviations exist: collection listing uses list_ for announcements/release_notes but get_ for tokens/users/audit_logs, and geocode is a lone bare verb.

    Tool Count2/5

    36 tools is well beyond the comfortable MCP scope and mixes content CRUD, auth/token administration, user management, audit logs, moderation workflows, and address utilities into one server. While no tool is redundant, the surface is too large for an agent to quickly select among eight subdomains.

    Completeness4/5

    Core lifecycles are well covered for places (search/detail/create/update/delete/stats), announcements, release notes, tokens, and moderation queues. The notable gap is no get_announcement_detail endpoint, and user management is limited to list/update_role/restore without user creation or deletion, but these can be worked around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources