Anythink Cli vs Stigmer

A side-by-side look at the Anythink Cli and Stigmer MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Anythink Cli logoAnythink CliCloud Platforms · Local subprocess (stdio)Build and run a complete backend from your agent on the Anythink platform: relational data with row-/field-level security, full-text + semantic + geo search, RBAC + BYOK, a workflow/automation engine, a growth & retention engine (email, actionable push, promotions, per-user referral codes + rewards, points/credits), payments + marketplace billing, and a growing catalog of integrations (Claude, OpenAI, Slack, Google, GitHub…) — driven through one CLI-backed MCP tool. Install with npx -y @anythink-cloud/mcp.67GreatAuth: otherStigmer logoStigmerCloud Platforms · Remote HTTP/SSEExecution graph of AWS: verified method contracts, IAM permissions, and least-privilege policies.55GoodAuth: not declared

Verdict: choose Anythink Cli for cloud platforms work as a local process; choose Stigmer for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Anythink Cli logoChoose Anythink Cli when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: other.
  • You want tools like config_use, projects_delete, login_direct.
Explore Anythink Cli

Stigmer logoChoose Stigmer when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like query, list_services, list_methods.
Explore Stigmer

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAnythink Cli logoAnythink CliStigmer logoStigmer
CategoryCloud PlatformsCloud Platforms
Quality signal67/100 · Great55/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthotherNot declared
PricingFreemiumNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars60
Directory activity 5 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools168

Tools & capabilities

Anythink Cli tools 16

  • config_useSwitch the active project profile that the 'cli' tool's commands operate against. Use this to move between already-connected projects without re-authenticating. The profile must already exist (created by 'projects_use' or 'login_direct'); run 'config_show' to see available profile names. Returns confirmation, or an error if the profile does not exist.
  • projects_deletePermanently delete a project and tear down its backend instance, including its database and stored data. This is destructive and irreversible — always confirm with the user first, and prefer matching by a specific id over a short prefix to avoid removing the wrong project. Requires an active billing account (set one with 'accounts_use'). Returns the deleted project's name and id on success.
  • login_directStore credentials directly for a project (bypasses billing login). Use this when you already have an org ID and API key or JWT token.
  • projects_useConnect to a project and save it as the active profile so the 'cli' tool's data, entities, users, and other commands target it. Resolves the project, then either stores the API key you pass or exchanges a transfer token for project-scoped credentials automatically. Requires an active billing account (set one with 'accounts_use'); the project must be Active (see 'projects_list'). Returns the saved profile name, org id, API URL, and auth method.
  • logoutRemove the saved credentials for a project profile from local CLI config. Use this to disconnect from a project or clear a stale token; it deletes only the stored profile locally and does not revoke the token server-side or affect the project. Omit the profile to remove the currently active one. Run 'config_show' to see profile names.
  • signupRegister a brand-new Anythink platform account with email and password. Use this only when the user has no account yet; if they already have one, use 'login' instead. This creates the top-level user identity — it does not create a billing account or project (do that with 'accounts_create' and 'projects_create' after logging in). On success the user may need to click an email confirmation link before 'login' works; tell them to confirm, then call 'login'.
  • accounts_createCreate a new billing account (organization) to hold projects and payment details. Requires a prior platform login (use the 'login' tool first). The new account is automatically set as the active account, so subsequent 'projects_create' / 'projects_list' calls target it without further setup. Returns the new account's id and name. Most users need only one account — call 'accounts_list' first to check whether a suitable one already exists.
  • config_removeDelete a saved project profile from the local CLI configuration. Removes only the locally stored credentials and settings — it does not delete the project or revoke tokens server-side (to remove the project itself, use 'projects_delete'). Run 'config_show' to see profile names. Returns confirmation, or a not-found message.
  • projects_listList the projects (provisioned backend instances) in a billing account. Requires platform login and an active billing account (set one with 'accounts_use'). Returns each project's id, name, description, region, org id, status (Initializing/Provisioning/Active/Suspended/Terminated/Error), API URL, and creation date. Use this to find a project's id before connecting with 'projects_use' or removing it with 'projects_delete'.
  • loginLog in to the Anythink platform with email and password. Returns a session token used for account and project management. For Google sign-in, use the 'login_google' tool.
  • accounts_useSet the active billing account that project commands operate on. Call this after 'login' when you belong to more than one account, before using 'projects_list', 'projects_create', or 'projects_use'. Accepts a full account UUID or a unique prefix; run 'accounts_list' to see valid ids. Returns the resolved account name and id, or an error if no account matches.
  • login_googleSign in to the Anythink platform with Google. Opens the user's browser to Google's consent screen and waits for them to approve, then stores the session token. The browser step must be completed by the user; everything before and after is tool-driven. This does NOT pick a billing account or project — after it returns, call 'accounts_list' then 'accounts_use', and 'projects_list' then 'projects_use'. Needs a local browser, so it only works over stdio (not the hosted HTTP server).
  • +4 more on the listing page

Stigmer tools 8

  • querySearch for verified method contracts for any library. Pass any text -- library name, method, what you're building, or an error you hit.
  • list_servicesList all libraries and services that have verified method contracts. Use this first to discover what's available, then query for specific methods.
  • list_methodsList all methods for a given library or service. Use after list_services to drill into a specific one.
  • policyGenerate a least-privilege IAM policy for an AWS workflow. Pass a named workflow, explicit IAM actions, or a description. Returns the exact policy with confidence tier and any unresolved operations.
  • list_workflowsList the curated named workflows that can generate least-privilege IAM policies.
  • verifyFeed a generated policy back to AWS's own policy evaluation engine (SimulateCustomPolicy) and confirm it grants exactly the intended operations and nothing extra. Returns verified (True|False|unknown), grants_all, grants_extra. Requires AWS credentials; without them verified=unknown with the reason. Wildcarded operations are expanded to concrete actions first.
  • authorizePre-flight authorization check for an AWS operation. Resolves the IAM actions the operation requires, then asks AWS's own policy simulator (SimulatePrincipalPolicy) whether the current role (or a given principal) allows them. Returns resolution (exact|partial|unresolved) and evaluation (allowed|denied|unknown) as separate fields. Requires AWS credentials; without them evaluation=unknown with the reason.
  • registerRegister a fix. Three actions: confirm (it worked), append_thread (variant worked), new_receipt (nothing matched, I fixed it).

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Anythink Cli

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "anythink-cloud-anythink-cli": {
      "command": "npx",
      "args": [
        "-y",
        "@anythink-cloud/mcp"
      ]
    }
  }
}

Stigmer

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "stigmer": {
      "url": "https://stigmer.network/mcp"
    }
  }
}

Frequently asked questions

Anythink Cli is categorized under Cloud Platforms and uses a local stdio subprocess. Stigmer belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Anythink Cli for cloud platforms work and Stigmer for cloud platforms.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Anythink Cli is listed as freemium — a free tier with paid plans. Auth: other. Stigmer has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add anythink-cloud-anythink-cli and stigmer as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Anythink Cli has a quality signal of 67/100 (Great) with 5 views, 0 installs and 6 GitHub stars. Stigmer has 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars.