Skip to main content
Glama
anythink-cloud

Anythink-MCP

Official
by anythink-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to Anythink-MCP

  • stripe by stripe

    stripeofficial

    stripe
    A
    license
    Not graded
    quality
    C
    maintenance
    The Stripe Model Context Protocol server allows you to integrate with Stripe APIs through function calling. This protocol supports various tools to interact with different Stripe services.
    21,341 npm
    1,949
    -

  • RevenueCat to Adapty Migration

    ferrousguy
    A
    license
    Not graded
    quality
    Not graded
    maintenance
    A Model Context Protocol server that helps users migrate subscription businesses from RevenueCat to Adapty through natural language interactions with LLMs like Claude Desktop.
    MIT

  • Directus MCP Server

    Skeyelab
    A
    license
    A
    quality
    C
    maintenance
    Enables comprehensive management of Directus instances through tools for schema manipulation, content CRUD operations, and dashboard management. It allows AI assistants to programmatically interact with collections, fields, relations, and workflow automation using the official Directus SDK.
    20
    14 npm
    MIT

Related Servers

  • mekka

    yiaany
    F
    license
    Not graded
    quality
    A
    maintenance
    A compact backend platform exposing a scoped MCP server for agents, with SQLite data plane, embedded Studio, auth, storage, and realtime. Default read-only agent access with opt-in read-write mutations via isolated preview branches and exact-SQL approval before production promotion.
    265 npm
    21
    -

  • SettleMesh

    StructureIntelligence
    A
    license
    Not graded
    quality
    A
    maintenance
    Deploy and monetize agent-built apps from one MCP. Ship a full-stack app (login, database, usage billing) with one command, then charge the signed-in end user per API call via X-Settle-Payer (end-user-pays: cost times markup, app owner earns the markup).
    Apache 2.0

  • TaskLite MCP

    tasklite-net
    A
    license
    A
    quality
    A
    maintenance
    Enables building a full backend directly from MCP clients using natural language, including projects, boards, typed columns, data, and REST endpoints with API keys. It also supports deploying frontends and provides a ready-made admin interface for end clients.
    48
    460 npm
    MIT

  • Aaly

    candysiva
    A
    license
    Not graded
    quality
    C
    maintenance
    A remote MCP server that lets a coding agent turn a plain-language idea into a real, shareable product — creating the project and data model, serving live API endpoints, deploying custom endpoints and server-side functions, and reading request and function logs. It handles sign-up, OAuth-backed access, and OpenAPI spec generation so people can open, sign into, and use the app the agent builds.
    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

C2.8/5.0

Scored across 102 tools

Disambiguation3/5

Many tools are clearly scoped by resource and action, but the 102-tool surface creates overlap: `cli`, `fetch`, and `api` can all be used for API access, while `integrations_connect` vs `integrations_oauth_connect` and several workflow helper tools require careful selection. Descriptions help, but the sheer number increases misselection risk.

Naming Consistency4/5

Names predominantly follow a consistent snake_case resource_action pattern (e.g., `entities_create`, `fields_update`, `workflows_step_add`). A few bare commands like `fetch`, `docs`, `api`, `cli`, `login`, `logout`, and `signup` are minor deviations from that pattern.

Tool Count1/5

With 102 tools, this far exceeds the normal 3-15 range and the 50+ extreme-mismatch threshold. A generic `cli` and `fetch` already cover broad functionality, so many individual tools are over-provisioned rather than essential.

Completeness4/5

The surface covers most domain lifecycle areas: auth, billing, projects, entities, fields, data, files, search, workflows, integrations, secrets, roles, users, API keys, and payments. Some resource-specific gaps remain (e.g., user update, menu item management), but the generic `cli`/`fetch` tools provide workarounds.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources