Skip to content
EN
Get API key
Browse documentation

Get started

FlashData MCP

Give your agent Google Search and YouTube tools. Connect your host, then ask for your first result.

On this page

1. Connect and sign in

Choose Codex or OpenClaw for browser-based OAuth. For another host, choose Remote / API key if it supports Streamable HTTP and custom headers, or Local / stdio if it launches MCP processes. The hosted server needs no local installation.

Merge the config below into ~/.codex/config.toml, then run the login command. Complete FlashData signup or sign-in and consent in the browser. Start a fresh Codex session after login.

config.toml
[mcp_servers.flashdata]
url = "https://data.flashdata.dev/mcp"

[mcp_servers.flashdata.oauth]
client_id = "flashdata-codex"
callback_url = "http://127.0.0.1/callback"
Sign in
codex mcp login flashdata --scopes mcp:research

2. Check the connection

Send this in a fresh agent session. Expect successful get_pricing and get_balance calls, an available price for google_search and your available credit balance. A zero balance means you need credits for the search; it does not mean authentication failed.

Connection check
Use the existing flashdata MCP connection.
Call get_pricing with {"source":"google_search","request_count":1}.
Call get_balance with {}.
Report whether both calls succeeded, whether the source has an available price,
and the available credit balance. A zero balance is not an authentication failure.
Do not run a search or download, create a trial, or change credentials.

3. Ask for your first task

Paste this into your connected agent. The balance and pricing checks are free; the search uses account credits.

First task prompt
Use FlashData to check my balance and the price of one Google search. If there are enough credits, call google_search once with query "battery recycling research", num 5 and mode "realtime". Return titles, source URLs, short excerpts and actual credits used. Stop after this task.

Check the result

Your agent should return source links and excerpts, plus the actual credits used. The underlying search result has status: done and results[].organic. An empty result is valid; the agent should report it. The example below is illustrative.

Example answer
Completed one Google search.
1. Battery recycling research — https://example.org/recycling
   An example search excerpt.
Credits used: 0.02

Available tools

API-key calls use the permissions granted to that key. Discover the server's tools and input schemas for the full current catalog.

TaskToolAccess
Search Googlegoogle_searchmcp:research / API key
Find YouTube videosyoutube_searchmcp:research / API key
Read video metadatayoutube_metadatamcp:research / API key
Retrieve existing captionsyoutube_transcriptmcp:research / API key
Download video or audioyoutube_downloadOwner API key + destination storage
Check account and pricingget_balance, get_pricing, get_limits, get_usageFree account reads

About OAuth, permissions and trials

OAuth connects your verified owner account and lets the host store and refresh tokens. The mcp:research grant covers the four research sources above. API-key connections use a protected X-API-Key header and can include other authorized sources.

To try FlashData before creating an account, use the CLI trial flow. MCP OAuth connects an owner account; it does not register or claim a trial. A CLI profile is not automatically shared with your MCP host.

Troubleshooting

ProblemTry this
No FlashData toolsFinish consent, reconnect and start a fresh session. Check the URL and Streamable HTTP transport.
invalid_client / callback errorFor Codex or OpenClaw, use its exact client configuration and a browser that can reach the local callback. For another host, use its supported API-key or stdio setup above.
401Reconnect expired or revoked OAuth access, or check the API key supplied to the host. Repeat the free check.
403Check the requested source and key permissions. YouTube Download requires an owner API key with youtube_download and destination storage; mcp:research does not include it.
402Check Billing and the current price. Reconnecting a valid credential does not add credits.
429Follow Retry-After. Keep any existing job or result ID before deciding whether to retry the task.
Timeout or incomplete responseKeep the request ID and check History. Read large-result continuations with get_result instead of repeating the search.

Go further