Skip to main content
Glama
Sign In
Eversports Studio Manager MCP Server

Eversports Studio Manager MCP Server

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Eversports Studio Manager MCP Server

No user-submitted related servers found.

    Related Servers

    • Mangomint MCP Server

      cotlet-connect
      A
      license
      A
      quality
      C
      maintenance
      Connects a signed-in Mangomint account to Claude Code, ChatGPT, Cursor and other AI agents so they can book and move appointments, check daily schedules and stylist gaps, reply to client messages, and pull client lists using plain language. No Mangomint API key or public API is required, since the server works directly inside the user's own Mangomint account.
      7
      Elastic 2.0

    • AestheticsPro MCP Server

      cotlet-connect
      A
      license
      A
      quality
      B
      maintenance
      Connects AestheticsPro accounts to ChatGPT, Claude, and other AI agents through Cotlet, enabling appointment scheduling, client contact access, lead creation, and staff assignment with user approval.
      7
      Elastic 2.0

    • Partiful MCP Server

      cotletdev
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents and scripts to read and manage events on your account — guest lists with questionnaire answers, CSV export, check-in, approvals, invites and Text Blasts — through your own signed-in Chrome session, with no public API or official integration required. Runs locally over stdio, streamable HTTP, a REST API with OpenAPI docs, and a Python client.
      2
      14
      147 PyPI
      7
      Elastic 2.0

    • AKIMCP

      yves7239
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables web-based AI chat clients such as Claude, ChatGPT, and Grok to read, edit, and run things on your own machine — files, shell commands, search, Git, SQLite, browser automation, DevTools, background tasks, localhost APIs, clipboard, and Postman — through a single OAuth-gated endpoint. Access is governed by a strict command whitelist and folder-scoped permissions rather than unrestricted shell access.
      MIT

    • Tradify MCP server

      cotletdev
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to read and change jobs, job status, customers, quotes with line items, invoices, quote and invoice email, payments, and Scheduler bookings in an account by reusing the user's own signed-in Chrome session, with no official API keys needed. Ships read-only hints and confirmation prompts for tools that reach other people, and can be run over stdio or streamable HTTP.
      2
      22
      403 PyPI
      6
      Elastic 2.0

    • meetup-mcp

      cotlet-connect
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to create, copy, and manage events in a user's own signed-in Meetup account through natural language, without requiring a Meetup API key. It works over HTTP or locally via stdio, forwarding tool calls to a hosted backend.
      7
      Elastic 2.0
    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

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a distinct step in a browser-automation lifecycle: guide (documentation), status (account/connection check), open (navigate), read (page snapshot), click, type, and close. The only mild adjacency is guide vs. status, but their descriptions clearly separate 'how to work' from 'is my account ready'.

    Naming Consistency5/5

    All seven tools use the same snake_case prefix `eversports_studio_manager_` followed by a short verb (guide, status, open, read, click, type, close). The pattern is entirely predictable and readable.

    Tool Count5/5

    Seven tools is a tight, well-scoped set for a single-site browser automation surface; every tool earns its place and nothing looks redundant. No filler or speculative operations are present.

    Completeness4/5

    The core loop (open → read → click/type → close) plus onboarding and status checks covers the stated purpose. Minor gaps exist for common browser interactions such as scrolling, selecting from dropdowns, or waiting for page load, which agents may have to work around with repeated read/click calls.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources