↔Data ConnectorPowered by Loam Data
DOCUMENTATION

Connect data to your MCP client.

Data Connector works with clients that support remote Streamable HTTP MCP servers and OAuth. Connect live PostgreSQL or MySQL directly, or import a supported file at dataconnector.ai.

Connect live PostgreSQL

Create a dedicated role that can connect and read only the required schemas and relations. Do not use an owner, migration, or application-write credential.

GRANT CONNECT ON DATABASE analytics TO mcp_reader;
GRANT USAGE ON SCHEMA reporting TO mcp_reader;
GRANT SELECT ON ALL TABLES IN SCHEMA reporting TO mcp_reader;

The endpoint must use a public hostname and TLS with hostname verification. Data Connector rejects private, loopback, link-local, reserved, mixed unsafe DNS, and cloud-metadata destinations. Private networking is not available today.

Sign in at dataconnector.ai, choose a workspace, enter the endpoint and read-only credential, and optionally allow only named schemas. Testing and future queries go through the Data Connector API. Passwords and custom CA material are write-only.

Connect live MySQL

Choose MySQL in the connection form and use a dedicated user with SELECT access only to the required database and tables. Use a public hostname with a valid TLS certificate, test the connection, and save it. MySQL uses the same four live-data MCP tools as PostgreSQL.

Import CSV, Parquet, or SQLite

Choose a Data Connector workspace and upload the file at dataconnector.ai. CSV and Parquet files create a queryable table. For SQLite, select a source table from the file to import. Read the CSV guide, the Parquet guide, or the SQLite guide.

Connect Google Search Console with Google OAuth

Use a Google account that already has access to the exact Search Console properties you want to read. Google provider authorization is separate from signing in to your Loam account and from authorizing an MCP client.

  1. Sign in at dataconnector.ai and choose a workspace. In Add data, select Business apps, Google Search Console, then Google OAuth and direct controls. A workspace administrator must create the connection.
  2. Enter a connection name and the exact properties, one per line, up to 20. Domain properties such as sc-domain:example.com and URL-prefix properties such as https://example.com/ are distinct. Authorize the intended Google account when prompted. Read-only Search Console access is requested first; no service-account JSON key is required.
  3. Connect your MCP client and choose the saved connection, exact properties and individual read permissions on its consent screen. Nothing is selected automatically. The client must request the additional mcp:gsc scope; legacy mcp:read consent alone does not expose Search Console tools.
  4. Ask a question or use a permitted task in Search Console controls. Check the exact property, reporting dates, fetch time and completeness notes in the result. A direct Google API read can still describe delayed or incomplete reporting data.

The direct profile can query search analytics, list or describe permitted properties, list or describe sitemaps, and inspect Google's indexed version of a selected URL. URL Inspection does not run a live test or request indexing.

Example: ask your AI to compare clicks and impressions for two equal finalized weeks, show the exact property and dates, identify which pages changed most, and explain missing query coverage. Reporting dates use America/Los_Angeles. Google can omit private queries and limit returned rows. Do not reconstruct property totals by summing query or page breakdowns, add CTR values, or average average-position values without their impression weights.

Direct results pass to the client you authorize; Connector does not save provider rows, reports or query results. Connector retains encrypted provider credentials, connection settings and security/workflow metadata. Saving an import, analysis result or file is a separate action through Data or Files with its own permissions. Read the privacy and retention details.

Optional sitemap and property changes

Read-only access is the default. Where provider changes are available, the Google OAuth profile supports four changes: submit a sitemap, remove a sitemap submission, add a property to your Google account, or remove a property from your account. Adding a property does not verify ownership or automatically select it for analytics. Removing a property does not delete the website, its index entries or imported Data tables. Sitemap changes do not edit the sitemap file on your website.

  1. As a workspace administrator, open Search Console controls for the connection. Select Enable selected provider write actions and the individual actions you need, then Save property and action policy. Choose Review additional Google write consent and authorize the intended Google account. Google write consent alone does not enable connection permissions or MCP access.
  2. Authorize your MCP client for the exact connection, properties and individual actions. Changing the connection policy can require fresh MCP consent. Ask it to prepare one specific change, such as submitting an existing sitemap URL for a selected property.
  3. Open Review a prepared write in Search Console controls and load the operation ID from your MCP client. Review the requesting client, property and exact effect, then choose Approve this exact effect. A tool cannot approve itself.
  4. Return to the original requesting MCP client to execute the approved operation. Approval is bound to that client authorization and exact effect. Check the operation status before preparing any further change.

If controls show Unavailable in this release, provider changes cannot be sent. If an operation is uncertain, use Check observed state without repeating the write and review Google's current state. Do not retry blindly: an uncertain result can mean Google received the change. Closing an uncertain operation does not repeat, undo or prove its effect. A new attempt needs a new preview and approval.

Reconnect or remove access

Google access, current property rights, workspace membership and MCP-client grants are separate checks. If the Google account loses access, a token expires without a usable refresh grant, or authorization is revoked, reads stop and the connection may require reconnecting. Reconnecting does not revive an old MCP approval or silently broaden its properties.

Choosing Disconnect this OAuth profile stops future use by that connection without silently requesting Google-wide revocation. Revoke the application's Google access in your Google account when needed. The separate Review Google-wide revocation action can affect grants and tokens for the same Google Cloud project, including other connections; review that impact first. Previously saved Data tables have their own permissions and are not deleted by disconnecting. Never paste provider tokens or keys into an AI conversation.

Existing service-account reporting snapshots

The separate Service-account reporting snapshots profile remains read-only. Enable the Search Console API in your Google Cloud project, create a service-account JSON key, and grant that service account property access in Search Console. Enter the key only in the signed-in connection form and select the exact properties. All three report tables are explicitly imported into Data: daily property totals, page performance and query performance.

That profile's default report covers 28 days ending three days before today in Pacific Time. Questions read the last successfully imported snapshot; use manual sync to refresh it and check the report dates. Google quotas, privacy filtering and errors can limit a refresh. Google OAuth does not silently replace a service-account credential or refresh an imported snapshot. Return to the Search Console task and example.

Connect Stripe

Create a Stripe restricted key with read permissions for Account and all ten supported resources. Start in test mode; test and live keys read different records. In Add data, choose Business apps and Stripe, enter the key. The connection imports all ten supported resources. Keep the key secret and use a different workspace or disconnect the existing connection to change account or mode. One Stripe connection is supported per workspace. See the Stripe connector.

Available resources are customers, charges, subscriptions, invoices, products, prices, balance transactions, payment intents, refunds and payouts. Keep currencies separate and distinguish gross payments, refunds and net amounts. These tables do not establish a certified MRR, tax or accounting calculation.

Refresh imported business data

The service-account Search Console profile and Stripe explicitly import selected records into Data-owned workspace tables. Questions about those tables read the last successfully imported data. The Google OAuth Search Console profile reads Google directly and does not require this import or refresh workflow. Use manual sync to refresh provider snapshots. Provider quotas and errors can prevent a refresh; check the connection status and report dates. Refresh replaces the selected report or resource snapshot after successful extraction rather than appending duplicate records; changes to older Stripe records can be reflected in a later sync. Provider requests do not form a transactionally consistent snapshot.

Add Data Connector to your MCP client

Add https://dataconnector.ai/api/mcp as a remote or custom MCP server, start the connection, complete OAuth in your browser, and authorize the workspace you want the client to use.

Exact setup steps vary by client. See the general MCP setup guide. For Claude web, desktop, or Claude Code, use the Claude-specific guide.

Available tools

  • list_data_sources, search_data_catalog, describe_data_source, and query_data_source provide bounded live PostgreSQL and MySQL access.
  • list_tables, describe_table, and execute_sql_query provide bounded access to every permitted managed table, including files imported from CSV, Parquet, and SQLite.

The Google OAuth Search Console profile adds gsc_query_search_analytics, gsc_list_properties, gsc_get_property, gsc_list_sitemaps, gsc_get_sitemap, and gsc_inspect_indexed_url only when the current connection, property and MCP consent permit them. Optional writes use gsc_submit_sitemap, gsc_delete_sitemap, gsc_add_property, and gsc_remove_property with separate prepare and execute phases when available and authorized. Use gsc_get_operation to check status; human approval and uncertain-state review happen in Search Console controls. These do not alter the seven database/table tools or their read-only SQL policy.

PostgreSQL and MySQL discovery and queries use the live source. Reads are not snapshots, so concurrent upstream changes can affect results.

SQLite Editorby Loamstack

Explore Data Connector