Model Context Protocol (MCP) is a new, standardized protocol for managing context between large language models (LLMs) and external systems.
peaka-mcp-server is an MCP project maintained in the peakacom/peaka-mcp-server repository. The maintainer describes its purpose as “Model Context Protocol (MCP) is a new, standardized protocol for managing context between large language models (LLMs) and external systems”. Read the project documentation for the complete scope.
The documented npm package is @peaka/mcp-server-peaka. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.
The example declares PEAKA_API_KEY. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| peaka_list_projects | List all projects accessible with the current API key. For Partner API keys, enumerates projects across all organizations and workspaces. For Project API keys, |
| peaka_query_golden_sqls | Query question/sql pairs from Peaka's golden sql vector store. If an existing query matches the user's question, it can be reused directly. |
| peaka_execute_sql_query | Runs the given sql query on Peaka. |
| peaka_get_project_metadata | Get metadata for all catalogs, schemas, and tables in the Peaka project in a single call. Optionally filter by catalogId and/or schemaName. |
| peaka_list_catalogs | List all available catalogs in the Peaka project. Returns catalog names, types, and connection info. |
| peaka_list_schemas | List all available schemas for a given catalog in the Peaka project. |
| peaka_list_tables | List all available tables for a given catalog and schema in the Peaka project. |
| peaka_list_columns | List all columns for a given table in the Peaka project. Returns column names, data types, and constraints. |
| peaka_get_relations | Get table relationships (foreign keys) for a catalog. Useful for constructing accurate JOINs. |
| peaka_get_table_statistics | Get column-level statistics for a table, including distinct-value fractions per column. |
| peaka_create_cache | Create a cache for a table in the Peaka project. Caching a table improves query performance by storing the data locally. |
| peaka_create_cache_batch | Create caches for multiple tables in a single call. Preferred over repeated peaka_create_cache calls. |
| peaka_get_cache_statuses | Get all cache statuses for tables in the Peaka project, including current caching state, execution history, and progress. |
| peaka_refresh_cache_full | Trigger a full refresh on an existing cache. |
| peaka_refresh_cache_incremental | Trigger an incremental update on an existing cache, fetching only new or changed rows. |
| peaka_update_cache | Update cache settings (schedules) on an existing cache. Replaces both schedules entirely each call. |
| peaka_delete_cache | Delete an existing cache; the underlying table is not affected. |
| peaka_list_queries | List all saved queries in the Peaka project. Returns query names, SQL content, and whether they are plain or materialized. |
| peaka_get_query | Read a single saved query by its ID. Returns the full query object including SQL, type, and the materialized-query refresh schedule. |
| peaka_execute_query | Execute a saved query by its ID in the Peaka project. |
| peaka_create_query | Create a named, saved query in the project's semantic layer. Returns the created query including its ID. For materialized queries, accepts an optional schedule |
| peaka_update_query | Update an existing saved query's display name, SQL body, and/or auto-refresh schedule (interval, cron, or {type: "none"} to disable; materialized queries… |
| peaka_delete_query | Delete a saved query from the Peaka project. |
| peaka_refresh_materialized_query | Trigger a refresh on a materialized saved query. Use peaka_list_queries to find query IDs whose queryType is MATERIALIZED. |
| peaka_get_materialized_query_statuses | Inspect the auto-refresh state of materialized queries: last refresh status, last/next scheduled execution, and schedule settings. Pass a queryId for a… |
| peaka_list_connections | List all data source connections in the Peaka project, including each connection's id, name, and type. |
| peaka_get_connection_detail | Get connection-specific configuration detail for a data source connection. |
| peaka_create_semantic_catalog | Create a semantic catalog in the Peaka project. A semantic catalog groups semantic tables (saved queries surfaced as queryable tables) under a single… |
| peaka_create_semantic_table | Create a semantic table inside a semantic catalog, backed by a saved query. Requires catalogId, schemaName, tableName, and queryId. |
| peaka_delete_semantic_table | Delete a semantic table from a semantic catalog. The underlying saved query is not affected. |
| peaka_refresh_project_metadata | Refresh project metadata for a specific catalog. Long-running; triggers the refresh and polls for completion. |
| peaka_get_metadata_refresh_status | Check the current status of a metadata refresh job for a specific catalog. |
{
"mcpServers": {
"peaka": {
"command": "npx",
"args": [
"-y",
"@peaka/mcp-server-peaka@latest"
],
"env": {
"PEAKA_API_KEY": "YOUR_PEAKA_API_KEY"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| PEAKA_API_KEY | Declared in the maintainer’s client configuration. | Check documentation |
Inspect PostgreSQL schemas and run read-only queries with the archived MCP reference server. Review its maintenance status before choosing it.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.