Data Connector

ai.dataconnectorPublished by dataconnector.aiOfficial publisherv0.1.0Updated Nov 7, 2026

Read authorized Loam tables and supported external databases through a bounded MCP connection.

VerifiedStreamable HTTPWeb executableDatabases

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant read authorized Loam tables and supported external databases through a bounded connection.

What you can do
  • Read authorized Loam tables
  • Read supported external databases
  • Access is limited to data the connected account is already authorized for, over a bounded connection
When to use it
When you want an assistant to query tables and databases you already have access to, without building a local connector.
Requirements
A remote MCP endpoint at dataconnector.ai reached over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
OAuth grants the server access to your data, so review which Loam tables and external databases are authorized. The description does not state whether any tool can write or change data; confirm before relying on it for read-only use.

Installation

In SourceWeft

  1. Open Data Connector in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.dataconnector%2Fdata-connector/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "data-connector": {
      "type": "http",
      "url": "https://dataconnector.ai/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestNov 7, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.