Skip to main content
Glama

DataCharter

Query all your data locally. Hand agents exactly the columns you choose.

A local SQL workspace over files and databases, federated by DuckDB and governed by charter.yaml. Agents get read-only, PII-masked access to what the contract grants. Apache-2.0. No paid edition.

PyPI Python License: Apache-2.0

datacharter.dev · Docs · Desktop · GovBench · Deploy

Two ways in. Same kernel.

Laptop

Drop a file. Query it. Chart it. An agent sees ••• where PII lives.

uvx datacharter serve          # demo workspace, http://127.0.0.1:8321
# or: datacharter init --from && datacharter serve
# or: datacharter init --template life && datacharter serve --local

No terminal: desktop app (beta). macOS (Apple Silicon) or Windows. Unsigned until Apple secrets exist.

brew install datacharter/tap/datacharter   # macOS
pip install datacharter                    # Python 3.11+

The workspace is a directory: charter.yaml, queries/, guides/. Commit it. Secrets stay out. Optional agent: SpaceXAI, Claude Code, Ollama (--local), or any OpenAI-compatible endpoint.

Related MCP server: orchard-data-mcp

Company

The same binary, on a shared MCP endpoint. Identities live in git, not on our servers. No rows leave your infrastructure.

datacharter mcp --http --host 0.0.0.0   # OAuth env required off loopback
helm install datacharter ./chart \
  --set oauth.issuer=... --set oauth.audience=... --set oauth.jwksUri=...
datacharter govbench --json             # cite corpus govbench-v1
  • MCP Streamable HTTP (POST /mcp) with optional OAuth 2.1

  • principals: and grants: in charter.yaml (default-deny on HTTP)

  • Helm chart and OCI image

  • Hash-chained audit plus SIEM JSON/OTLP

  • GovBench: frozen 28-attack corpus, grade A-F

Wrap someone else's MCP server: datacharter mcp --guard "npx -y some-mcp-server".

What the contract enforces

PII default-deny, row filters, plain-English policies (aggregates only), canaries, a flight recorder, datacharter redteam, access diff on PRs. CLI reference: docs/cli.md. Security: docs/security.md.

Status: pre-release. V1 in development.

Privacy

Runs on your machine or in your cluster. No telemetry. No DataCharter-operated data plane. Privacy Policy.

License

Apache-2.0

Available Tools

6 tools
describe_tableDescribe tableA
Read-onlyIdempotent

Show columns and types for one relation (e.g. 'crm.customers').

Inputs: relation (required).

list_metricsList certified metricsA
Read-onlyIdempotent

List certified metrics — name, what each computes, its dimensions, and whether it supports a time grain. Prefer query_metric over writing SQL when a metric matches the question.

Inputs: no named parameters.

list_sourcesList data sourcesA
Read-onlyIdempotent

List configured data sources with their types.

Inputs: no named parameters.

list_tablesList tablesA
Read-onlyIdempotent

List all queryable tables with their fully-qualified relation names.

Inputs: no named parameters.

queryRun read-only SQL queryA
Read-onlyIdempotent

Run a read-only SQL query and return rows. Use fully-qualified relation names. Prefer LIMIT for exploration.

Inputs: sql (required).

query_metricRun a certified metricA
Read-onlyIdempotent

Run a certified metric by name and return its governed result. Optionally group by dimensions (by) and/or a time grain.

Inputs: name (required), by, grain.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct action: enumerating sources, tables, or metrics; describing schema; running raw SQL; or running a governed metric. The only near-overlap, query vs query_metric, is explicitly disambiguated by naming and by the guidance in list_metrics.

    Naming Consistency5/5

    Tool names follow a predictable verb_noun pattern: list_* for enumeration, describe_table for schema inspection, and query/query_metric for data retrieval. Naming is uniform and intuitive.

    Tool Count5/5

    Six tools is a well-scoped number for a data discovery and querying server. Each tool covers a necessary step in the workflow—source discovery, table discovery, schema inspection, raw query, metric discovery, and metric query.

    Completeness5/5

    The tool set provides a complete read-only analytics flow: discover sources and tables, inspect schemas, run SQL, list certified metrics, and query those metrics. There are no obvious missing operations for its stated purpose.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      F
      maintenance
      Read-only MCP server for SQL databases (SQL Server, Postgres, SQLite) with multi-server support and three-layer safety using AST validation and linting.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Pay-per-call MCP server for market data with USDC micro-payments, featuring unique ML market-regime forecasts, news catalyst radar, and a live-verified algorithmic trading track record.
      12
      68 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A read-only DuckDB MCP server offering context-efficient analytics tools (list_datasets, describe_table, profile_column, explain, query) with a semantic layer for business rules, security guards, and disclosed truncation to help LLMs produce correct answers while minimizing token usage.
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A safe, read-only MCP server for local development databases (PostgreSQL and SQLite) that provides guarded introspection tools like schema listing, sample rows, and explain plans with column masking and query budgets.
      MIT