Amnesic vs MCP Clickhouse — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Amnesic vs MCP Clickhouse
In-depth architectural comparison of the Amnesic and MCP Clickhouse MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Amnesic
Databases · Local stdio
Quality: 55/100 (Good) | Auth: other
MCP Clickhouse
Databases · Local stdio
Quality: 65/100 (Great) | Auth: other
Verdict Summary: Choose Amnesic if you need specialized Databases tools running via a local process. Choose MCP Clickhouse if your workspace requires Databases integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Amnesic when:
You need dedicated capabilities in the Databases domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
The MCP server that remembers your database — persists table/column annotations, an FK relationship graph, and searchable notes across sessions, so the model stops re-discovering your schema every time. PostgreSQL, MySQL, MSSQL, SQLite; read-only-enforced.
ClickHouse database integration with schema inspection and query capabilities
Amnesic is categorized under Databases and uses a local stdio subprocess. In contrast, MCP Clickhouse belongs to Databases using local stdio subprocess. Select Amnesic when you need capabilities focused on databases and MCP Clickhouse when you require tools for databases.
List available ClickHouse tables in a database, including schema, comment,
row count, and column count.
Args:
database: The database to list tables from
like: Optional LIKE pattern to filter table names
not_like: Optional NOT LIKE pattern to exclude table names
page_token: Token for pagination, obtained from a previous call
page_size: Number of tables to return per page (default: 50)
include_detailed_columns: Whether to include detailed column metadata (default: True).
When False, the columns array will be empty but create_table_query still contains
all column information. This reduces payload size for large schemas.
Returns:
A JSON-encoded string of an object containing:
- tables: List of table information (as dictionaries)
- next_page_token: Token for the next page, or None if no more pages
- total_tables: Total number of tables matching the filters
run_query
Execute SQL queries in ClickHouse. Queries run in read-only mode by default. Set CLICKHOUSE_ALLOW_WRITE_ACCESS=true to allow DDL and DML operations. Set CLICKHOUSE_ALLOW_DROP=true to additionally allow destructive operations (DROP, TRUNCATE).