Skip to main content
Glama
Sign In
Lichess MCP

Lichess MCP

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Lichess MCP

No user-submitted related servers found.

    Related Servers

    • LinkedIn MCP Server

      cotlet-connect
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to operate a user's signed-in LinkedIn account, including scheduling posts, replying to comments and messages, inviting leads, finding prospects, and summarizing unread messages without a LinkedIn API key or developer app.
      Elastic 2.0

    • Assertify

      romaklym
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to browse, click, type and read on any website the user is logged in to, using encrypted local sessions with multiple named accounts per site. It behaves like a human, asks for confirmation before risky actions, and hands control back for CAPTCHAs or 2FA.
      28
      MIT

    • mcp-server-linkedin

      gxm097
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to use an existing browser session to read profiles and companies, search jobs and people, and manage messages and connection requests on LinkedIn.
      21
      Apache 2.0

    • LinkedIn MCP Server

      AndresMinakata
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to browse profiles and companies, manage messages and inboxes, and search jobs, posts, and people through a locally logged-in browser session. All actions run on the user's own machine.
      19
      Apache 2.0

    • open-browser-control

      smankoo
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to control the user's Chrome or Firefox browser, leveraging existing sessions for tasks requiring authentication and user handoff.
      18
      58 npm
      21
      MIT
    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 loop: guide/status for setup, open for navigation, read for page inspection, click/type for interaction, and close for teardown. There is no meaningful overlap between any pair, so an agent can select the right tool unambiguously.

    Naming Consistency4/5

    All tools share a consistent lichess_ prefix and snake_case style, which is predictable and readable. Two tools (guide, status) are nouns rather than verbs while the rest are action verbs, a minor deviation from a strict verb_noun pattern.

    Tool Count5/5

    Seven tools is a tight, well-scoped set that covers the full browser automation lifecycle for the stated Lichess workflow without filler. Each tool clearly earns its place.

    Completeness4/5

    The core loop (open, read, click, type, close) plus setup (guide/status) fully covers the 'accept team join requests and message team' purpose. Minor gaps exist—no explicit scroll, back/navigate, or wait/screenshot—but the read+click+type combination lets agents work around most of these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources