クエリ ストリーム MCP

Let your AI think.
We’ll handle the heavy data work.

Find the right tables. Turn large results into compact findings. Keep the data ready for the next question.

Query Streams gives your AI client a partner beside your databases: the Network Agent. Less data to read and move. Fewer repeated requests. More room to work through your question.

Start with FreeSee it in action

Table discovery and read-only queries on Free.
Profiling and follow-up analysis from Personal Core.

A Network Agent works beside two databases inside a building, sending a compact findings card to an AI client outside.
The groundwork happens beside your data.Your AI client uses the findings to reason, explain and follow up.

Why Query Streams MCP?

Because getting a useful answer takes more than running a query. Your AI client needs to find the data, make sense of it and ask the next question.

Find the right place to start.

A short question finds relevant tables by meaning, even among thousands of coded names. Your AI client reads the schema it needs and gets on with the query.

Less searching. Fewer guesses.

Spend tokens on useful context.

The Network Agent profiles and analyses large results beside your database. Your AI client receives compact findings it can use to decide what to explore next.

Less raw data to read and transfer.

Ask the next question without starting over.

Filter, group, compare or sample a held result. Follow-up tools reuse the data already on the Network Agent, without another database query.

Fewer round trips. Less repeated work.

Work with private data on your terms.

The Network Agent connects out from inside your network. Database credentials stay there, and queries pass a read-only check before they reach your data.

No inbound database ports or VPN.

Table discovery is included on Free

Start with the right tables.

Your AI client asks for what it needs in plain words, in any language. Query Streams returns a short, ranked list of matching tables, with a reason for each match. Then your AI client reads the columns it needs and writes the query.

  • Ask in your language. Find tables by meaning.Search names, columns and descriptions across a captured database. Semantic Intelligence can add meaning to abbreviated names, and your team’s table choices help improve future searches.
  • Works across the whole captured database.New captures become searchable within minutes. Table and description changes are reflected automatically. Finding a table does not query your database.

Measured in development tests on November 6, 2026: about 60 ms median per search; 71 of 72 questions across 12 languages found the right table in the top three. Results vary by database and question.

Your AI client asks

Find vehicle auction history, then count the records.

A ranked shortlist, with reasons qs_find_tables
  1. auc_uaxmtn.conlibv_pfarbhist1,048 rows · Match in description
  2. auc_uaxmtn.conlibv_pfvehcond2,258,576 rows · Name match: vehicle
    Read as: vehicle condition

Next: read the matching table's schemaqs_get_table_schema
database: asi
table: auc_uaxmtn.conlibv_pfarbhist

Then: run the read-only querySELECT COUNT(*) AS history_rows
FROM auc_uaxmtn.conlibv_pfarbhist;

Illustrative auction-database exchange using table names and row counts from development testing. Reply shortened for readability.

See what your AI can do with a head start.

Once the right data is found, the Network Agent can profile it, calculate over it and keep it ready for follow-up questions. Choose an example to see how a large result becomes something your AI client can explain.

Your AI client or Nova
  • ノヴァ
モデルを使用し、何を尋ねるかを判断します。
ネットワーク・エージェントクエリストリームProfiles and analyses data beside your databases.
請求書をプロファイリングして、回収の優先順位を付ける保存済みクエリ：請求書分析
分析例
パーソナルコアとアップ
  1. 請求書の結果を把握する

    行を読む前にデータをプロファイリングします。

    Nova or your AI client needs to understand a large invoice result. It asks for a local profile, rather than reading batches of invoices to discover the columns and values.

    AI はまず、データの簡潔な概要を確認します。

    Nova or your AI client

    この請求書データの結果には何が含まれていて、延滞残高の回収に役立つ項目はどれですか？

    詳細を尋ねる前に、結果を把握します。
    保存されたクエリ: 請求書分析
  2. 最適化されたツール：結果のプロファイリング

    大量の請求書データの結果をプロファイリングします。

    エージェントはデータベースのそばで結果をスキャンし、列の統計、範囲、一般的な値を返します。AI はすべての行を自ら処理しなくても、請求書の分析方法を把握できます。

    モデルのコンテキストに含まれる未加工データが少ないほど、処理するトークンとインターネット経由で転送するデータが減ります。

    ネットワーク内のNetwork Agent
    請求書分析対応SQLサーバー
    クエリ結果をプロファイリングqs_run_saved_query / モード: profile
    184,902プロファイルを作成した行数
    6列
    選択した列の分析結果
    請求書 ID欠損値 0 件
    額1,140.00～28,900.00
    ステータス未処理、期限超過、支払い済み
    地域北、南、東、西
    結果全体をローカルに保持AI はプロファイルを受け取ります。エージェントは次の計算に備えて行を保持します。
  3. フォローアップツール: 保持した結果をクエリする

    必要な合計を尋ねる。

    プロファイルによって、AI は必要なフィールドを把握できます。AI はエージェントに、ローカルに保持済みの結果を使って、期限超過の請求書を絞り込み、地域別に残高をグループ化するよう依頼します。

    この例では、データベースへの2回目のクエリはありません。

    Nova or your AI client follows up

    期限超過の残高を地域別にグループ化します。どこから始めましょうか？

    保持された結果を使用保持した結果から期限超過の請求書を絞り込み、地域別に SUM(amount) を計算する。
    エージェントは、データのそばで同じ結果を再利用します。
  4. 説明できる4つの合計

    残高の大きい順に並べる。

    エージェントは地域別の合計を4つ返します。AI は請求書の行を何度も要求、読み取り、合算する代わりに、回収の優先順位に集中できます。

    この分析では184,902行をローカルに保持します。フォローアップへの回答は、グループ化された4行です。

    ネットワーク内のNetwork Agent
    期限超過の残高をローカルでグループ化qs_result / op: query
    地域期限切れ
    南28,900.00
    北17,320.80
    イースト9,765.25
    ウエスト5,493.95
    合計61,480.00
    184,902行をローカルに保持。このフォローアップでは、要約行を4行 AI に返します。
    AIが説明できるようになりました

    期限超過額の75.2%を南部と北部が占めています。まずこの地域で回収を開始し、次に残りの地域の少額の残高に取り組みましょう。

データと簡略化したワークフローは説明用です。MCPリクエストは送信されません。プロファイリングと保持された結果へのクエリにはPersonal Core以上が必要です。セグメンテーション、異常検知、比較にはBusiness Core以上が必要で、プランの上限が適用されます。Freeには標準の読み取り専用MCPクエリが含まれます。

同じNetwork Agentの基盤が支えるのは 組み込みAIアナリストのNovaです.

The Network Agent advantage

The heavy work belongs beside your data.

Profiles, calculations and held results stay close to the database. Your AI client receives the findings it asks for, with less data to transfer and less repeated processing.

Standard MCP queries return query results. With the optional analysis tools, your AI client can request a compact profile or calculation instead of the full result.

  • Your database credentials stay inside.Your AI client signs in to Query Streams or uses a revocable MCP key. It never needs your database password.
  • One outbound, encrypted connection.Requests and results travel over a connection opened by the Network Agent. Your database needs no inbound port or VPN for Query Streams.
  • Read-only is enforced beside the data.The Network Agent checks every query and refuses statements that would change your data.

Bring the data your business actually runs on.

Use the same MCP connection across supported databases, files, logs and API-connected services. Saved queries and cross-source queries give your AI client more ways to work with the data you already have.

Explore supported sources
  • データベースSQL Server, PostgreSQL, MySQL, Oracle and more, on your network or in the cloud.
  • ファイルとログWork with CSV, Excel, Parquet and log data through supported file connectors.
  • Connected servicesQuery service data and join it with your other sources, within your plan limits.

Start free. Add deeper analysis when you need it.

無料

Find the right tables and run read-only queries. Use saved queries and join up to two sources.

  • Table discovery in plain language
  • One API key, 30 calls per minute
  • Up to 1,000 rows per query
Free is a plan. It never expires.

個人的な核心

Give your AI client compact findings and data it can reuse.

  • Size checks and column profiles
  • Compact result summaries
  • Held results for follow-up questions
Less data work in the AI conversation.

ビジネスコア

Go deeper into quality, patterns and changes across your data.

  • データ品質チェック
  • 異常、セグメント、比較
  • Nova、内蔵AIアナリスト
More ways to investigate what matters.

Features are available within each plan’s allowances. Compare plans and limits

Connect your data once. Bring your AI client.

Install the Network Agent on Windows, Mac or Linux and connect your data sources. Then connect your AI client through SSO or a revocable MCP key.

SSOでサインイン

For AI clients that support sign-in

AIアプリにQuery Streamsを追加し、Query Streamsアカウントでサインインしてアクセスを承認します。APIキーをコピーする必要はありません。

APIキーで接続

APIキー接続に対応するツール向け

ポータルの接続ウィザードで、いつでも無効化できるMCPキーを作成し、サーバーアドレスとキーをツールの設定に追加します。

Server settings for API-key clients
"querystreams": { "url": "https://mcp.querystreams.com/mcp", "headers": { "X-MCP-Key": "your key" } }

どちらの方法でも、データベースのログイン情報はNetwork Agent上に留まります。ポータルからいつでもアクセスを取り消せます。

ステップバイステップガイドFind Query Streams in your AI client’s connector directoryOr use Nova, the AI analyst built into Query Streams

人々が最初に尋ねる質問

Does it work on a very large database?

Yes. Your AI client asks for what it needs and gets matching tables ranked, with a reason for each match, whether the database has 40 tables or 20,000. It can find the right table without reading the whole list.

Does my AI need to know my table names?

No. Your AI client can ask in plain words, in any language. Table names, column names, descriptions and captured sample values help find matches. Semantic Intelligence can add meaning to abbreviated or coded names, but it is optional.

Does finding a table use my data allowance?

Only the small reply itself. Finding a table reads nothing from your database.

What happens right after I connect a big database?

It becomes searchable within minutes of schema capture, with nothing to configure. Until then, your AI client is told the index is still building and how far along it is, and it can list tables the usual way. Changes to tables and descriptions are reflected automatically.

Does finding a table send my schema to an AI vendor?

Finding a table runs entirely inside Query Streams; no third-party AI service performs the search. Your connected AI client receives the matching table names and reasons. If it asks for a table’s schema or query results, those replies are returned to that client too.

ポートを開放したり、VPNを実行したりする必要はありますか？

No. The agent runs inside your network and opens one outbound, encrypted connection to Query Streams. Requests and results travel both ways over it. Your AI client connects to Query Streams, never to your database, so there is no inbound port, no IP allowlist and no VPN. The agent runs on a laptop, a VM, on-prem hardware or any cloud that allows outbound HTTPS.

SSOまたはAPIキーを使えますか？

Yes. If your AI client supports SSO, connect with your Query Streams account. For clients that use API-key authentication, create a revocable MCP key in the portal and add it with the server address. Your database login stays on the Network Agent with either method.

私のAIクライアントは私の行を認識していますか？

Standard MCP queries return query results to your AI client. Optional profiling and analysis tools send compact findings instead of the full result. Held results stay on your Network Agent, and your AI client receives only the rows or summaries it requests.

保留結果とは何ですか？

A result your AI client asks the agent to keep for a while. Follow-up questions are answered from that copy, with no second database query: filter it, group it, sort it, page through it or take a sample. Query Streams' servers never store those rows. It is released when its hold time ends, when the assistant releases it, or when someone clears held results on the Data Agents page. Held results are on Personal Core and up.

AIがデータの書き込みや削除を試みたとしたらどうなるでしょうか？

すべてのクエリは、データベースに到達する前にエージェント上で読み取り専用チェックを受けます。SELECT、WITH、EXPLAINは実行できます。それ以外は拒否されます。このチェックはクラウドではなく、ネットワーク内で行われます。

どのプランに含まれていますか？

Table discovery and read-only MCP queries are included on every plan, including Free. Free never expires and includes one key, 30 calls a minute and up to 1,000 rows per query. Profiling and held-result analysis start on Personal Core; deeper analysis starts on Business Core. Nova, the AI analyst built into Query Streams, starts on Business Core. プランを比較する.

Give your AI a head start on its next answer.

Find the right tables. Let the Network Agent prepare the data. Give your AI client more room to think.

無料プランを入手