Skip to main content
Glama
lindoai

mcp-lindoai

Official
by lindoai
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

Related Servers

Alternatives to mcp-lindoai

No user-submitted related servers found.

    Related Servers

    • Tempreon by Tempreon

      Tempreonofficial

      Tempreon
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides a portable personal knowledge layer for AI tools, enabling cross-LLM continuity and personalized context across clients like Claude, ChatGPT, and Cursor.
      -
    • automatelab-ai-seo by AutomateLab-tech

      automatelab-ai-seoofficial

      AutomateLab-tech
      A
      license
      A
      quality
      C
      maintenance
      AutomateLab AI-SEO audits, scores, and rewrites web pages for AI citation eligibility, AEO and GEO. No API keys or registration. Works with Claude, Cursor, Codex, and other MCP clients. Product and documentation: https://automatelab.tech/products/mcp/ai-seo/
      20
      62 npm
      3
      MIT

    • VibeKit MCP

      VibeKit-Bot
      A
      license
      A
      quality
      B
      maintenance
      MCP server for VibeKit — build, deploy, and manage hosted apps and chat with each app's persistent server-side AI agent from Claude Desktop, Cursor, or any MCP client. Every app gets its own agent and a live URL; bring your own Claude/OpenAI key or pay-as-you-go.
      36
      17 npm
      1
      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

    B3/5.0

    Scored across 50 tools

    Disambiguation4/5

    Tools are broadly separated by resource (workspace, client, website, page, blog) and action, and the async workflow/batch variants are clearly scoped. Minor ambiguity exists between create_blog (AI-generated) and publish_blog (static markdown), and get_credits vs get_client_credits requires reading descriptions to distinguish.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (list_websites, create_client, delete_page, unpublish_blog), with batch/check variants following the same convention. Small inconsistencies like get_workspace_team vs add_workspace_team_member and unprefixed get_credits vs get_client_credits keep it from a 5.

    Tool Count1/5

    At 50 tools, this is an extreme count for a single MCP server; even with a broad CMS scope, the agent surface is very large. Many workflow starters and their polling/batch counterparts inflate the surface and would be better grouped behind fewer tools or explicit sub-resources.

    Completeness5/5

    The surface covers nearly full lifecycles for workspaces, clients, websites, pages, and blogs, including CRUD, publishing, analytics, team management, credits, custom domains, and async workflows with batch status polling. No obvious dead ends or critical missing operations exist for the stated platform domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources