MCP Tools4Foresight

Read-only MCP server for the foresight signals from tools4foresight.com. It gives an agent access to the same map a member sees: curated signals, the semantic graph, themes with their history, and the three horizons.

It writes nothing. There is not a single tool that modifies, publishes, or deletes anything. See SECURITY.md.

What an agent can do with this

• "What is the state of the map?" → H1/H2/H3 overview with its macro-themes.

• "Which themes are growing and which are fading?" → time series per theme.

• "Summarize the AI agents theme" → profile with its four indicators and its signals.

• "What is similar to this signal?" → semantic neighbors, without leaving the curated map.

• "What weak signals are there in H3?" → small themes with high novelty.

• "What died this month?" → fossils, by comparing snapshots.

Related MCP server: AI Knowledge Base MCP Server

Installation

You need a tools4foresight API key (ask whoever administers it).

Claude Code

claude mcp add tools4foresight \
  --env T4F_API_KEY=tu-api-key \
  -- npx -y mcp-tools4foresight

Claude Desktop

In claude_desktop_config.json:

{
  "mcpServers": {
    "tools4foresight": {
      "command": "npx",
      "args": ["-y", "mcp-tools4foresight"],
      "env": { "T4F_API_KEY": "tu-api-key" }
    }
  }
}

Cursor

In .cursor/mcp.json, the same block as Claude Desktop.

Remote (HTTP)

If you prefer to deploy it once and have several agents use it, see docs/DEPLOYMENT.md. The remote endpoint requires its own credential (MCP_ACCESS_TOKEN), different from the API key.

There is a complete example in .mcp.json.example.

Environment variables

The 18 tools

Full reference with examples in docs/TOOLS.md.

Plus 7 resources, to attach context by hand from Claude Desktop or Cursor: foresight://overview, ://glossary, ://horizons, ://signal/{id}, ://theme/{id}, ://horizon/{key}, and ://macro-theme/{id}.

And 6 prompts —suggested conversation scripts, which give no extra capability— for the questions that come up repeatedly: analizar_horizonte, informe_de_tema, radar_semanal, senales_debiles, comparar_temas, and explorar_desde_senal.

This server is for exploring: publishing, unpublishing, editing the analysis, or recomputing the graph are still done from tools4foresight, and none of that is exposed here.

Three things worth knowing before reading the output

1. A signal's date is an estimate. The X API does not expose when a like happened, only the order. That is why likedAt is always shown with ~.

2. A dead theme is a fossil, not a deletion. It is kept and can be revived. Nothing is removed from the map.

3. The similarity percentage is not shown to a person. A 0.63 reads as a precision the method does not have. strength (strong/medium/weak) is used instead; the raw score is available for the agent's reasoning.

The full glossary of the method is in docs/DOMAIN.md and can be queried live with explain_foresight_term.

Documentation

License

The code is MIT. The content it serves is not: the signals and the tools4foresight map are paid subscription material.