Blog

Connecting AI to your data.

Notes on MCP, database access, and keeping AI tools local to your infrastructure.

Written by the people building Bufflehead. No newsletter gate — read and go.

2026-11-13

One less cloud dependency between your AI and your data

During Claude’s November 13 connector disruption, our local Bufflehead connection kept working. What local MCP removes from the path—and what it still depends on.

2026-10-31

Connect your data visually. Ask AI through MCP.

Save database connections in Bufflehead, connect your AI assistant through native MCP, and let it discover schemas and query the source you choose.

2026-10-20

Why we prefer local, per-user MCP database access

Shared service credentials add identity and access-control work. Our preferred default is a local AI bridge, scoped user credentials and corporate-managed endpoints.

2026-10-17

Ask your database questions without handing AI a delete button

How Bufflehead configures read-only connections, what each database enforces, and why restricted database permissions provide a separate boundary.

2026-10-16

Same database, different churn: agree on the metric before asking AI

A tested synthetic subscription example produces 25% customer churn and 10% gross MRR churn. Define the cohort and calculation before asking an AI tool to query the data.

2026-10-14

Read-only doesn't mean cheap: cap BigQuery query costs

Estimate an agent query with a dry run, enforce a maximum-bytes-billed limit, and distinguish a per-query guardrail from a total spending budget.

2026-10-13

Similar isn't eligible: check the conditions before recommending an order

A tested synthetic order fixture checks status, amount and date boundaries together. Separate exact eligibility, missing evidence and optional ranking before trusting an AI recommendation.

2026-10-12

SQL shows the drop. Does the document explain it?

A tested synthetic revenue example separates a measured decline from a supplier memo's proposed explanation. Keep SQL facts, document claims and causal uncertainty visible.

2026-10-11

Which items need restocking? Let the agent read before anyone orders.

A tested Postgres inventory fixture separates sellable stock, confirmed receipts and reorder thresholds from supplier lookup and purchase approval.

2026-10-10

Can you trace that AI answer back to the SQL?

Preserve the question, SQL and returned rows together. A synthetic review-record demo separates an incorrect query from a summary that contradicts its result.

2026-10-08

A successful SQL query can still double-count revenue

A tested Postgres fixture shows why one-to-many joins inflate totals and SUM(DISTINCT amount) loses equal-valued orders. Define the metric grain before trusting an AI answer.

2026-10-07

The agent stopped. Did it answer the question?

Compare two bounded query budgets against a known-answer fixture. Record what remains unknown when the loop stops, and keep completion checks in the client.

2026-10-05

The missing table: why SQL access still needs a map

A tested Postgres order lookup shows why stock alone does not establish fulfilment eligibility. Supply the table relationships and business rule, then inspect the SQL.

2026-10-01

Who's asking? Give every agent query a name.

Give an AI agent a scoped read-only Postgres role, then find its session in the database logs. A tested walkthrough with real log lines, and what Bufflehead does and does not do.

2026-09-29

Cheaper tokens ≠ cheaper deployments

Measure AI deployment cost per successful outcome with read-only Postgres SQL. Include retries and failures, check billing coverage, and keep unit cost separate from ROI.

2026-09-25

Why did paid installs drop? Query the rollup, check the coverage.

Check attribution import coverage before explaining an install drop. A read-only Postgres walkthrough for AI analytics, campaign comparisons, and correctly weighted rates.

2026-09-24

Ask before you query: when an AI should clarify revenue

Gross sales, paid orders, or revenue after refunds? A Postgres walkthrough showing when an AI should ask for a business definition before querying through read-only access.

2026-09-23

Your AI ran valid SQL. Did it answer the question?

Five Postgres checks for AI-generated SQL: totals, rankings, date boundaries, duplicate joins, and missing data. Verify the answer, not just whether the query runs.

2026-09-21

Was that the right price—on the order date?

Compare invoice prices with effective-dated catalog data using read-only Postgres SQL. Surface missing periods, overlapping prices, and currency or unit mismatches.

2026-09-20

Read-only SQL is not a data-access policy

Read-only access prevents writes, but does not decide which data an AI may read. Test a scoped Postgres role with allowed and denied queries through Bufflehead.

2026-09-19

Stop pasting your database into the prompt

Give AI useful database context with schema, relevant samples, and focused SQL. A read-only Postgres walkthrough inspired by Matthew Brown’s Claude demo.

2026-09-03

MCP Scoping and Permissions: Why "Three Read-Only Tools" Isn't Actually Read-Only

The tool boundary isn't the security boundary — query construction and credential grants are. Why read-only enforcement belongs at the connector layer, not just the DB layer.

2026-08-29

"The MCP server did it" is a bad line in your audit log

Query-logging and credential-attribution are different problems. Scrubbed views and pgaudit fix the first one; per-engineer credentials fix the second.

2026-08-26

Connecting Claude to MySQL or MariaDB: Three Architectures Compared

Remote MCP on the DB server, local MCP with a direct connection, or local MCP over an SSH tunnel — the tradeoffs that actually matter for stability, security, and maintenance.