Data Connector
Hosted OAuth MCP access to your data, including Google Search Console. Choose permitted sources; Search Console reads are the default and optional changes need human approval.
Hosted MCP Server
npx add-mcp 'https://dataconnector.ai/api/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
Connect your data. Choose what AI can do.
Ask Claude and compatible AI apps about your business using the numbers in your connected data. Start with read-only access. For Search Console, separately enable the sitemap and property changes you want and approve each exact effect.
- Sign in or sign up with Loam, then choose or create a workspace.
- Choose Add data. Connect PostgreSQL, MySQL or Google Search Console, import Stripe reports, or upload a CSV, Parquet or SQLite file.
- Add Data Connector in Claude or an OAuth-compatible MCP client, approve workspace access, then ask about your data.
File imports upload a copy to your workspace; processing is remote. Your original file stays unchanged and later changes are not synced.
Read-only by defaultYou choose what to shareHosted MCP server
Bring the conversation closer to your business.
Ask with context
Explore sales, compare periods, or investigate a change using the data you connect.
Use the data you have
Connect live PostgreSQL or MySQL, read selected Search Console properties or import Stripe reports, or import CSV, Parquet and SQLite files.
Keep control
Database and imported-table tools read permitted data. They cannot edit or delete that data.
Choose the data your AI can read
Use live database access for current PostgreSQL and MySQL data. Connect PostgreSQL with access to the data you choose.
Ask about a CSV file, a Parquet file, or an imported SQLite table. These file imports reflect the copy you upload.
Explore Google Search Console performance or Stripe payment and subscription data. The Google OAuth profile reads Search Console directly; Stripe and the separate service-account reporting profile use imported snapshots with manual refresh.
Read-only database and table access keeps queries from changing source data. Direct Search Console reads require their own selected property and read-action consent. Existing database authorization does not grant that access. Optional Search Console sitemap and property changes need additional Google consent, enabled actions, specific MCP permissions and human approval. Database and Stripe write actions are not available today.