Documentation Index
Fetch the complete documentation index at: https://docs.gildea.ai/llms.txt
Use this file to discover all available pages before exploring further.
Gildea provides an MCP (Model Context Protocol) server so AI assistants can use Gildea’s verified intelligence as a tool. We host the server publicly at https://api.gildea.ai/mcp — no Python, no terminal, no local install needed.
For users who’d rather run the server as a local subprocess, see Local install below.
Hosted server
The hosted server speaks the streamable-HTTP MCP transport and auths via the x-api-key header. Most clients let you paste these two values (URL + key) and you’re done.
Claude Desktop
-
Get your API key at gildea.ai.
-
Open your config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
- Windows:
%APPDATA%\Claude\claude_desktop_config.json
Create it if it doesn’t exist.
-
Add Gildea to the
mcpServers block:
{
"mcpServers": {
"gildea": {
"url": "https://api.gildea.ai/mcp",
"headers": {
"x-api-key": "gld_your_key_here"
}
}
}
}
-
Restart Claude Desktop. Click the tools icon in the chat input — Gildea’s 7 tools (
search_text_units, get_signal_detail, etc.) should appear automatically.
-
Try: “Use Gildea to search for verified claims about data center power constraints.”
Claude Code
claude mcp add gildea --transport http https://api.gildea.ai/mcp --header "x-api-key: gld_your_key_here"
Verify with claude mcp list — you should see gildea ✓ Connected with 7 tools.
Other MCP clients
Any MCP-compliant client that supports streamable HTTP / remote MCP can connect. Common config shape:
{
"type": "http",
"url": "https://api.gildea.ai/mcp",
"headers": { "x-api-key": "gld_your_key_here" }
}
See the MCP client list for per-client config syntax (Cursor, VS Code via Cline/Continue, etc.).
Local install (advanced)
For users who want to run the MCP server locally — air-gapped environments, self-hosted Gildea API instances, or developers iterating on the SDK — install via pip or uvx:
Prerequisite
Either uv (brew install uv) or a global pip install "gildea[mcp]".
Claude Desktop config
{
"mcpServers": {
"gildea": {
"command": "uvx",
"args": ["--from", "gildea[mcp]", "gildea-mcp"],
"env": {
"GILDEA_API_KEY": "gld_your_key_here"
}
}
}
}
Or with pip-installed binary:
{
"mcpServers": {
"gildea": {
"command": "gildea-mcp",
"env": { "GILDEA_API_KEY": "gld_your_key_here" }
}
}
}
Claude Code
claude mcp add gildea -- uvx --from "gildea[mcp]" gildea-mcp
# or
claude mcp add gildea -- gildea-mcp
Self-hosted Gildea API
If you’re running the REST API on your own infrastructure, point the local MCP server at it via env var:
"env": {
"GILDEA_API_KEY": "gld_your_key_here",
"GILDEA_API_BASE_URL": "https://your-api-host.example.com"
}
REST API vs MCP
Both access the same data. Choose based on your use case.
| REST API | MCP Server |
|---|
| Best for | Apps, dashboards, pipelines, custom agents | Claude Desktop, Claude Code, any MCP client |
| Protocol | HTTP/JSON | stdio (default) or SSE |
| Auth | X-API-Key header | GILDEA_API_KEY env var |
| Rate limits | Shared quota | Shared quota |
| Pagination | Cursor-based | Limit param (no cursors) |
| Data | Identical | Identical |
Rate limits are shared across REST and MCP. A request from Claude Desktop and a request from your app count toward the same per-minute and monthly quota.
The MCP server exposes 7 tools that mirror the REST API.
search_text_units
Search across Gildea’s verified text units — thesis sentences, argument sentences, summary sentences, and atomic claims. Every unit has been verified against source evidence; results are not direct quotes but sentence-level extractions.
Two modes:
q — free-text search. Returns the most relevant units across the corpus.
similar_to — pass a text unit ID; returns units with similar stored embeddings (useful for cross-source corroboration and “find more like this”).
Exactly one of q or similar_to is required.
Parameters:
| Param | Type | Required | Description |
|---|
q | string | One of q / similar_to | Free-text search query |
similar_to | string | One of q / similar_to | Text unit ID — finds similar units via stored embeddings |
unit_type | string | No | Filter: thesis_sentence, argument_sentence, summary_sentence, analysis_claim, event_claim |
entity | string | No | Entity public ID (e.g. gld:/a1b2c3d4e5f6). Returns only units literally mentioning the entity |
theme | string | No | Theme label (1 of 12). Returns units from articles tagged with that theme |
published_after | string | No | ISO 8601 date — only results from articles published after this date |
published_before | string | No | ISO 8601 date — only results from articles published before this date |
recency_boost | number | No | 0.0–1.0. Soft preference for newer results; default 0 (off) |
diversity_cap | integer | No | Max units per source article (1–100, default 2) |
verification_detail | string | No | full for complete verification metadata; default is compact |
limit | integer | No | Max results (default 10, max 100) |
Example prompt: “Search for verified claims about GPU supply constraints”
// Keyword search
{ "q": "GPU supply constraints", "unit_type": "analysis_claim", "limit": 5 }
Example prompt: “Find text units similar to this claim”
// Similar-to search
{ "similar_to": "0004c6d0e2f1a3b5c7d9e1f3a5b7c9d1e3f5a7b9", "limit": 5 }
list_signals
Find intelligence signals about the AI economy from 500+ expert sources. Each signal is a structured analysis or event report decomposed into verified components — use get_signal_detail to access the full tree. All filters are optional; without filters, returns the most recent signals.
Parameters:
| Param | Type | Required | Description |
|---|
entity | string | No | Entity ID filter |
theme | string | No | Theme label filter |
q | string | No | Text search query |
content_type | string | No | analysis or factual_event |
published_after | string | No | ISO date (e.g. 2026-02-01) |
published_before | string | No | ISO date |
limit | integer | No | Max results (default: 25, max: 50) |
Example prompt: “Show me recent analysis signals about OpenAI”
{ "entity": "gld:/e5f6a7b8c9d0", "content_type": "analysis", "limit": 5 }
get_signal_detail
Get the full verified reasoning chain for a signal. This is where Gildea’s value lives. Analysis signals expose a thesis, supporting arguments, and verified claims as siblings under decomposition. Event signals expose a summary and verified claims. Claims are served as a flat array at the article level, not nested under arguments. Each piece has been independently verified against source evidence. Use this tool liberally — it’s the difference between showing metadata and showing actual verified intelligence.
Parameters:
| Param | Type | Required | Description |
|---|
signal_id | string | Yes | Signal ID |
include | string | No | Set to evidence for source snippets |
verification_detail | string | No | Set to full for verification metadata |
Example prompt: “Get the full decomposition of that signal with evidence”
{ "signal_id": "0001f3a7b9c8d4e5f6a7b8c9d0e1f2a3b4c5d6e7", "include": "evidence" }
list_entities
Discover which companies, people, and products are getting expert attention in the AI economy. Filter by trend direction, notability, coverage scale, and more. Use this for discovery — finding what’s worth paying attention to.
Parameters:
| Param | Type | Required | Description |
|---|
q | string | No | Fuzzy name search |
theme | string | No | Filter by theme label |
type_primary | string | No | Filter by entity type |
sort | string | No | signal_count (default), first_seen, or trend |
direction | string | No | Rising, Stable, Declining, New |
confidence | string | No | Significant, Insignificant |
stability | string | No | Volatile, Steady |
scale | string | No | Large, Medium, Small |
notability | string | No | High, Medium, Low, Negligible |
limit | integer | No | Max results (default: 25, max: 50) |
Example prompt: “Show me reliably rising entities”
{ "direction": "Rising", "confidence": "Significant", "sort": "trend", "limit": 10 }
get_entity_profile
Get an intelligence profile for a company, person, or product. Returns whether the entity is rising, stable, or declining in expert coverage; how much attention it’s getting relative to others; whether the trend is statistically significant; and a notability assessment. Use this to understand an entity’s trajectory before diving into specific signals.
Parameters:
| Param | Type | Required | Description |
|---|
name_or_id | string | Yes | Entity name (fuzzy matched) or entity UUID |
Example prompt: “Show me NVIDIA’s entity profile”
{ "name_or_id": "NVIDIA" }
Entities with fewer than 8 mentions in the 12-week window return scale only. The direction, confidence, stability, and notability fields will be null due to insufficient data for statistical significance.
get_themes
List all taxonomy themes across two axes that categorize the AI economy. Each theme includes signal counts, trend direction, and notability. Use get_theme_detail for full trend analytics and co-occurring themes.
Parameters:
| Param | Type | Required | Description |
|---|
axis | string | No | value_chain or market_force |
Taxonomy:
- Value chain: Infrastructure, Foundation Models, Orchestration, Data & Labeling, Applications, Distribution
- Market force: Capital & Investment, Regulatory & Legal, Competitive Dynamics, Talent & Labor, Geopolitical Strategy, Trust & Societal Impact
Example prompt: “What value chain themes are trending?”
{ "axis": "value_chain" }
get_theme_detail
Get a specific theme’s full trend analytics and co-occurring themes from both axes. Returns trend direction, statistical confidence, stability, notability with reasoning, and which themes from the other axis most frequently co-occur. Use this to understand how themes interconnect.
Parameters:
| Param | Type | Required | Description |
|---|
axis | string | Yes | value_chain or market_force |
label | string | Yes | Theme label (e.g. Infrastructure) |
Example prompt: “Tell me about the Geopolitical Strategy theme”
{ "axis": "market_force", "label": "Geopolitical Strategy" }
Sample conversation
Here’s what a real interaction looks like when Claude Desktop has the Gildea MCP server connected:
You: What are the most important things happening in AI right now?
Claude: Let me check the latest market intelligence.
[Calls list_entities with direction=“Rising”, confidence=“Significant”, sort=“trend”]
[Calls get_themes with axis=“value_chain”]
Based on the latest signals from 500+ sources, here are the key dynamics:
Rising entities:
- OpenAI — Large scale, Rising direction, Significant confidence. Notability: High.
- Anthropic — Medium scale, Rising direction. Steadily gaining share.
Hottest themes:
- Infrastructure — Rising with high confidence. The GPU/compute build-out narrative continues to intensify.
- Regulatory & Legal — Significant upward trend driven by EU AI Act implementation.
You: Dig into what’s driving the Infrastructure theme.
Claude: [Calls get_theme_detail with axis=“value_chain”, label=“Infrastructure”]
[Calls list_signals with theme=“Infrastructure”, limit=5]
The Infrastructure theme has a Theil-Sen slope of 0.12 (Rising, Significant, Steady). Here are the latest signals driving it:
- “TSMC Accelerates CoWoS Capacity Expansion” — Analysis signal with 8 verified text units…
- “Microsoft Plans $80B Data Center Spend” — Event signal…
You: Search for anything about chip export controls.
Claude: [Calls search_text_units with q=“chip export controls”]
Found 10 verified text units across 7 signals. The top results include thesis sentences about supply chain restructuring and claims about NVIDIA’s H20 shipments to China…
Authentication & rate limits
The MCP server uses the same API key and rate limits as the REST API. Set your key via the GILDEA_API_KEY environment variable.
| Tier | Per-minute | Monthly |
|---|
| Hacker | 5 | 200 |
| Pro | 30 | 2,000 |
| Team | Custom | Custom (contact sales) |
Rate limits are shared — requests from MCP and REST count toward the same quota. When you exceed the limit, the tool returns an error message with the retry-after interval.
Troubleshooting
”Authentication failed”
The API key is missing, invalid, or revoked.
- Check that
GILDEA_API_KEY is set in your MCP config
- Verify the key starts with
gld_
- Check your key status on the dashboard
”Rate limit exceeded”
You’ve hit the per-minute or monthly quota.
- Check your current tier’s limits in the table above
- Wait for the retry-after interval (returned in the error message)
- Consider upgrading your tier if you consistently hit limits
- Restart Claude Desktop after editing the config file
- Check the config path is correct:
~/Library/Application Support/Claude/claude_desktop_config.json on macOS
- Verify the JSON is valid (no trailing commas)
- Check Claude Desktop logs for connection errors
SSE connection issues
- Ensure the port isn’t already in use:
lsof -i :8001
- Check that the server is running:
curl http://localhost:8001/sse should initiate a stream
- For remote connections, ensure firewalls allow the port
API connectivity issues
The MCP server connects to the Gildea REST API over HTTPS.
- Verify
GILDEA_API_KEY is set correctly
- If using
GILDEA_API_BASE_URL, check the URL is reachable: curl https://your-api-host/v1/health
- Check for network/firewall issues if you get connection errors