Skip to main content
Glama
Anythink-MCP

Anythink-MCP

Official

Related Servers

Alternatives to Anythink-MCP

  • 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,738 npm
    2,032
    -
  • 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
  • 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
    21 npm
    MIT

Related Servers

  • 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
    22
    -
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables coding agents to turn plain-English descriptions into live, typed, versioned HTTPS backend endpoints with auth and secrets handled, then call them — with each endpoint able to combine LLM reasoning, web search, scraping, media and voice generation, email, databases, storage and scheduled jobs. Also lets agents create and edit projects, list and inspect generated resources and runtime packages, and apply local manifest files.
    334 npm
    MIT
  • A
    license
    Not graded
    quality
    B
    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
  • 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
    818 npm
    MIT
  • 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

TDQS

A3.8/5.0

Scored across 175 tools

Disambiguation3/5

Descriptions are unusually thorough and cross-reference siblings explicitly ('use X instead of Y'), so most boundaries are clear. However, with 175 tools there are genuine overlaps: convenience wrappers (workflows_file_handler_add vs workflows_step_add), preview/get pairs (charts_preview vs dashboards_widget_preview vs dashboards_data), and catch-all escape hatches (cli, fetch, api) that duplicate the dedicated tools' scope. An agent must read carefully to pick correctly, so some overlap exists despite good prose.

Naming Consistency4/5

Names overwhelmingly follow a snake_case prefix_noun_verb or prefix_verb convention (email_templates_update, menus_update_item, dashboards_add_chart, pay_subscriptions_cancel, workflows_step_add). Minor deviations exist: several unprefixed top-level tools (login, signup, logout, docs, cli, fetch, api) and shorthand pay_* names break the resource-prefix pattern. Still largely predictable.

Tool Count1/5

175 tools is an extreme mismatch for a single MCP server, far past the 50+ threshold. Even granting that Anythink is a full backend platform, cramming project, entity, data, workflow, payment, email, auth, and search management into one surface is unwieldy and forces agents to select blind. This module should be decomposed into several scoped servers.

Completeness4/5

Coverage is remarkably broad: entities, fields, data, RLS, users, roles, menus, dashboards, charts, workflows, integrations, payments, email, search, secrets, files, API keys, projects and accounts all have full lifecycle tools. Only minor, explicitly acknowledged gaps exist (no refund tool, no way to remove a single offer code, no trigger-editing tool), which agents can work around.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive