Skip to content
Agentmart
Submit a tool

FutureSearch MCP Server

Forecast questions about the future, including the outcome under each option.

Connector by futuresearch · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 57
Write a review

Chalk Labs

Need help deploying FutureSearch MCP Server?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/futuresearch-futuresearch-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Forecast questions about the future, including the outcome under each option.

Use cases: deep-research, data-analysis

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools
9 read · 12 write · 1 delete
Secrets
1 (API keys, tokens or passwords)
Install scripts
None found
Runs as
Python package

Tools by what they do 22

Read from the source code; the running server may list different tools.

Read 9 · Look things up without changing anything.

  • futuresearch_balance
  • futuresearch_browse_lists
  • futuresearch_list_session_tasks
  • futuresearch_list_sessions
  • futuresearch_progress
  • futuresearch_results
  • futuresearch_status
  • futuresearch_task_cost
  • futuresearch_task_data

Write 12 · Create, change, send or run things.

  • futuresearch_agent
  • futuresearch_classify
  • futuresearch_decision
  • futuresearch_dedupe
  • futuresearch_forecast
  • futuresearch_merge
  • futuresearch_multi_agent
  • futuresearch_rank
  • futuresearch_request_upload_url
  • futuresearch_task_download
  • futuresearch_upload_data
  • futuresearch_use_list

Delete 1 · Delete, drop, revoke or wipe things.

  • futuresearch_cancel

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • FUTURESEARCH_API_KEY

Network hosts it talks to 13

  • cohort-engine.cohort.svc.cluster.local · found in code
  • cohort-staging-engine.cohort-staging.svc.cluster.local · found in code
  • fonts.googleapis.com · found in code
  • fonts.gstatic.com · found in code
  • futuresearch.ai · found in code
  • github.com · found in code
  • glama.ai · found in code
  • host.docker.internal · found in code
  • iliivszxpymuffgrwsws.supabase.co · found in code
  • jmraczchpxwbrnngyjuf.supabase.co · found in code
  • mcp-staging.futuresearch.ai · found in code
  • mcp.futuresearch.ai · found in code
  • unpkg.com · found in code

Tools (22)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • futuresearch_agentRun Web Research Agents

    Run web research agents on each row of a CSV file. The dispatched agents will search the web, read pages, and return the requested research fields for each row. Agents run in parallel to save time and are optimized to find accurate answers at minimum cost. `task` describes WHAT to research in natural language. `response_schema` defines the OUTPUT STRUCTURE as a JSON Schema. If omitted, results default to a single {"answer": string} field. Pass it whenever you need typed or multi-field output. Do NOT describe desired output columns only in `task` — the schema is what controls the output struc…

  • futuresearch_balanceCheck Account Balanceread-only

    Check the current billing balance for the authenticated user. Returns the account balance in dollars. Use this to verify available credits before submitting tasks.

  • futuresearch_browse_listsBrowse Reference Listsread-only

    Browse available reference lists of well-known entities. Includes company lists (S&P 500, FTSE 100, Russell 3000, sector breakdowns like Global Banks or Semiconductor companies), geographic lists (all countries, EU members, US states, major cities), people (billionaires, heads of state, AI leaders), institutions (top universities, regulators), and infrastructure (airports, ports, power stations). Use this when the user's analysis involves a well-known group that we might already have a list for. Returns names, fields, and artifact_ids to pass to futuresearch_use_list. Call with no parameter…

  • futuresearch_cancelCancel a Running Taskcan change or delete data

    Cancel a running futuresearch task. Use when the user wants to stop a task that is currently processing.

  • futuresearch_classifyClassify Rows

    Deprecated: Classify each row of a dataset into one of the provided categories. Uses web research that scales to the difficulty of the classification. Each row is assigned exactly one of the provided categories. Examples: - "Classify each company by its primary industry sector" with categories ["Technology", "Finance", "Healthcare", "Energy"] - "Is this company founder-led?" with categories ["yes", "no"] - "Classify by Koppen climate zone" with categories ["tropical", "arid", "temperate", "continental", "polar"] Output columns added: the ``classification_field`` column (default: ``classific…

  • futuresearch_decisionDecision

    Forecast a decision: the outcome under each option, the user's or anyone else's. Causal decision support, e.g. "If I fund this organization at $0 / $300k / $2M, will it ship its study by 2027?" (binary), "…how many researchers will it hire?" (numeric), or "…when will it ship?" (date). Each row states the outcome question, and ``alternatives_field`` names a column holding that row's mutually exclusive alternatives as a JSON array (2-50 entries; a binary "do X / don't do X" decision is the 2-alternative case). The outcome is forecast under each alternative as its own hypothetical, all alternati…

  • futuresearch_dedupeDeduplicate Rows

    Deprecated: Remove duplicate rows from a CSV file using semantic equivalence. Dedupe identifies rows that represent the same entity even when they don't match exactly. The duplicate criterion is semantic and LLM-powered: agents reason over the data and, when needed, search the web for external information to establish equivalence. Examples: - Dedupe contacts: "Same person even with name abbreviations or career changes" - Dedupe companies: "Same company including subsidiaries and name variations" - Dedupe research papers: "Same work including preprints and published versions" This function s…

  • futuresearch_forecastForecast

    Forecast questions about the future using deep research. The ``forecast_type`` selects what kind of outcome you are forecasting: - **binary** (default): Forecasts probability (0-100) for YES/NO questions. Output columns: ``probability`` (int, 0-100) and ``rationale`` (str). - **numeric**: Forecasts percentile estimates for continuous numeric questions. Requires ``output_field`` (e.g. ``"price"``) and ``units`` (e.g. ``"USD"``). Output columns: ``{output_field}_p10`` through ``{output_field}_p90`` (float), ``units`` (str), and ``rationale`` (str). - **date**: Forecasts date percenti…

  • futuresearch_list_session_tasksList Tasks in a Sessionread-only

    List all tasks in a session with their IDs, statuses, and types. Use this to find task IDs for a session so you can display previous results with mcp__display__show_task(task_id, label).

  • futuresearch_list_sessionsList Sessionsread-only

    List futuresearch sessions owned by the authenticated user (paginated). Returns session names, IDs, and timestamps. Use this to find past sessions or check what's been run. Results are paginated — 25 sessions per page by default.

  • futuresearch_mergeMerge Two Tables

    Deprecated: Join two CSV files using intelligent entity matching. Merge combines two tables even when keys don't match exactly. Uses LLM web research and judgment to identify which rows from the first table should join those in the second. left = the table being enriched (ALL its rows appear in the output). right = the lookup/reference table (its columns are appended to matches). IMPORTANT defaults — omit parameters when unsure: - merge_on_left/merge_on_right: only set if you expect exact string matches on the chosen columns or want to draw agent attention to them. Fine to omit. - relatio…

  • futuresearch_multi_agentMulti-Agent Parallel Research

    Deep parallel research: deploys multiple agents on different angles, then synthesizes. Use this when either (a) completeness matters — you're trying to find all items matching a criteria (e.g. "all AI startups in Europe") and a single agent would have poor recall, or (b) depth matters — the answer benefits from parallel investigation across genuinely distinct angles (sources, geographies, methodologies) that one agent would weight unevenly. For list-generation tasks especially, directing agents at different slices (by region, by vertical, by time period) dramatically improves coverage before …

  • futuresearch_progressCheck Task Progressread-only

    Check progress of a running task. Blocks briefly to limit the polling rate. After receiving a status update with partial results, briefly comment on the new rows for the user, then immediately call futuresearch_progress again (passing the cursor from this response) unless the task is completed or failed.

  • futuresearch_rankScore and Rank Rows

    Deprecated: Score and sort rows in a CSV file based on any criteria. Dispatches web agents to research the criteria to rank the entities in the table. Conducts research, and can also apply judgment to the results if the criteria are qualitative. `task` describes how to score each row in natural language. `response_schema` optionally defines extra output columns as a JSON Schema. If omitted, only the score column is returned. Do NOT describe desired output columns only in `task` — the schema is what controls the output structure. Examples: - "Estimate this drug's peak annual sales in billion…

  • futuresearch_request_upload_urlRequest Upload URL

    Request a presigned URL to upload a local CSV file. Use this to upload a file from your local filesystem or sandbox. This is the recommended way to ingest local files in HTTP mode. Steps: 1. Call this tool with the filename (and optionally session_id to add to an existing session) 2. Execute the returned curl command to upload the file 3. Parse the JSON response to get the artifact_id and session_id 4. Pass the artifact_id to any processing tool (futuresearch_agent, etc.)

Show 7 more tools
  • futuresearch_results

    Retrieve results from a completed futuresearch task (text-only). Only call this if explicitly asked — the unified widget (futuresearch_status) handles result display automatically. page_size controls how many rows are included in the LLM response.

  • futuresearch_statusCheck Task Status (widget)read-only

    Check task status and display a live progress widget. Returns a progress widget that keeps itself up to date and shows the results once the task finishes. After calling this once, do NOT call futuresearch_progress — the widget refreshes itself. Only call futuresearch_results if the user explicitly asks to see or discuss the results in the chat.

  • futuresearch_task_costGet Task Costread-only

    Get the billed cost of a completed task. Returns the amount charged in dollars. There is a delay between task completion and cost calculation. Returns 'pending' if the cost hasn't settled yet.

  • futuresearch_task_dataTask Data (widget)read-only

    Widget-only. Not for use by an agent. The session widget calls this itself to refresh what it displays. Use futuresearch_status to show a user a task, or futuresearch_results to load row data into the conversation.

  • futuresearch_task_downloadTask Download Link (widget)

    Widget-only. Not for use by an agent. The session widget calls this to get a link it can open when someone asks to download a task's results. Use futuresearch_results to load row data into the conversation instead.

  • futuresearch_upload_dataProcess Data

    Upload data from a URL or local file. Returns an artifact_id for use in processing tools. Use this tool to ingest data before calling futuresearch_agent, futuresearch_rank, futuresearch_dedupe, futuresearch_merge, futuresearch_classify, or futuresearch_forecast. Supported sources: - HTTP(S) URLs (including Google Sheets — auto-converted to CSV export) - Local CSV file paths (stdio/local mode only — not available over HTTP) For local files over HTTP, use futuresearch_request_upload_url instead: 1. Call futuresearch_request_upload_url with the filename 2. Execute the returned curl command to …

  • futuresearch_use_listImport Reference List

    Import a reference list into your session and make it available via artifact_id for other futuresearch tools. This copies the dataset into a new session and returns an artifact_id that can be passed directly to other futuresearch tools (futuresearch_agent, futuresearch_rank, etc.) for analysis or research. The copy is a fast database operation (<1s) — no polling needed.

Signals

Stars
57
Forks
9
Open issues
1
Contributors
14
Weekly downloads
632
Last commit (this folder)
Oct 5, 2026 (25 days ago)
Last release
Oct 5, 2026 (25 days ago)
Last package publish
Oct 5, 2026 (25 days ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.futuresearch/futuresearch-mcp
Version
0.27.0
Auth
API key
Packages
pypi futuresearch-mcp
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from futuresearch

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get FutureSearch MCP Server running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying FutureSearch MCP Server?

CallGet help
Cite this page

FutureSearch MCP Server. Agent Mart. https://agentmart.dev/connectors/futuresearch-futuresearch-mcp (last updated 2026-10-24)