manage_memory_bounds

MCP tool from Localdata MCP by ChrisGVE

View and configure memory limits

How to use it

Project documentation lists manage_memory_bounds for the Localdata MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.

Install Localdata MCP

$localdata-mcp
FULL LOCALDATA MCP LISTING

Other tools in Localdata MCP (39)

analyze_anova

Statistical Analysis

analyze_clusters

Pattern Recognition

analyze_effect_sizes

Statistical Analysis

analyze_hypothesis_test

Statistical Analysis

analyze_query_preview

Estimate query cost before execution

analyze_regression

Regression and Modeling

analyze_time_series

Time Series

cancel_query_operation

Cancel a running or buffered query

check_compatibility

Verify API backward compatibility

clear_streaming_buffer

Free memory from a specific buffer

connect_database

Open a connection to any supported database or file

describe_database

Show schema and table list

describe_table

Column types, indexes, row count

detect_anomalies

Pattern Recognition

disconnect_database

Close a connection

evaluate_model_performance

Regression and Modeling

execute_query

Run SQL with streaming, chunking, and preflight mode

export_graph

Export as DOT, GML, GraphML, Mermaid, or Markdown

export_schema

Export schema as JSON Schema, Python dataclasses, TypeScript interfaces, or SQL DDL

export_structured

Export as TOML, JSON, YAML, or Markdown

find_path

Shortest path or all paths between two nodes

find_table

Locate a table across all active connections

forecast_time_series

Time Series

get_data_quality_report

Column statistics, null rates, and quality metrics

get_error_log

Recent error log

get_graph_stats

Node/edge counts, density, DAG validation

get_metrics

Prometheus metrics text. Registered only when metrics collection is enabled, which is the default

get_query_log

Recent query execution history

get_query_metadata

Rich metadata for a completed query

get_streaming_status

Check active streams and buffer usage

list_databases

List active connections

list_keys

List key-value pairs at a node

move_node

Relocate a node within the tree

next_chunk

Retrieve the next chunk of a streamed result

reduce_dimensions

Pattern Recognition

request_data_chunk

Fetch a specific chunk by row range

request_multiple_chunks

Batch-fetch multiple chunks in one call

search_data

Regex search across query results

transform_data

Apply column transformations to result sets