← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionStackQL MCP ServerQuery and provision cloud infrastructure with SQL.Basic MemoryYour AI never forgets again.
FMRS55 / 100 · C72 / 100 · B
Reliability9 / 2010 / 20
Security and permissions8 / 2015 / 20
Maintenance13 / 2016 / 20
Documentation12 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Teams needing a unified SQL interface across cloud and SaaS providers
  • Users who want AI agents to access cloud resources in a structured way
  • Cloud operations, security, FinOps, and infrastructure-as-code workflows
  • Privacy-conscious developers who want local data storage.
  • Researchers who need AI-assisted management of large note collections.
  • Users of Markdown editors like Obsidian.
Not for
  • Users who only need local file or browser automation
  • Environments that cannot grant cloud or SaaS API access
  • Users expecting a tool inventory with individually named MCP tools, which the source does not provide
  • Users needing cloud sync and mobile access (unless using the paid cloud service).
  • Minimalists who want zero configuration.
  • Scenarios requiring large-scale vector databases and complex retrieval (local SQLite may be insufficient).
Required permissions
  • Provider authentication must be supplied through --auth or the client configuration
  • Effective permissions depend on the provider credentials and requested operations; the server supports querying and provisioning
  • GitHub Actions defaults to read_only mode, which is intended as the safe CI default
  • Read and write to the local filesystem (default: ~/basic-memory).
  • Perform file and directory operations (create, edit, delete).
  • Access local SQLite database (or Postgres/Milvus if configured).
Risks and side effects
  • Provisioning or modifying resources can cause real infrastructure changes
  • Overprivileged credentials can broaden the impact across cloud or SaaS resources
  • AI-generated SQL or API operations should be reviewed before execution
  • Cross-cloud operations may create cost, compliance, and security consequences
  • Tools have write operations that may unintentionally modify or delete notes.
  • Edit operations may overwrite existing content, though there are protections.
  • Semantic search and reranking features may require model downloads, adding latency.
  • Local data backups are the user's responsibility.
Supported clientsClaude, VS Code, CursorClaude Desktop, Claude Code, Codex, Cursor, VS Code, ChatGPT, Obsidian
Tools021