Skip to main content

Model Context Protocol

The Radar is an MCP.

Pipe the AI native engineering tools radar straight into Claude Desktop, Claude Code, Cursor, Windsurf, or any MCP-aware client. Twenty-two tools, one HTTP endpoint, no auth — query the radar like it's a queryable, LLM-native data layer.

Tools
22
Auth
None
Cost
Free
Transport
HTTP
POST https://radar.creative-technology.digital/api/mcp/mcp

Discovery file: /mcp.json · See the integration guides to wire it into your client.

Integration Guides

Claude Desktop

  1. Open claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\).
  2. Add the mcpServers block below (merge with existing if present).
  3. Save and restart the application to connect.
{
  "mcpServers": {
    "signal-radar": {
      "url": "https://radar.creative-technology.digital/api/mcp/mcp"
    }
  }
}

ChatGPT

  1. MCP support is in beta via custom GPT actions — there is no JSON config file like other native clients.
  2. In the GPT builder, go to Configure > Actions > Create new action.
  3. Set the server URL to the endpoint below and choose "No authentication" (the Signal MCP server requires none).
https://radar.creative-technology.digital/api/mcp/mcp

Windsurf

  1. Open your Codeium MCP config at ~/.codeium/[editor]/mcp_config.json (create it if it does not exist).
  2. Add the mcpServers block below (merge with existing if present).
  3. Reload the editor or run the MCP: Reload Servers command.
{
  "mcpServers": {
    "signal-radar": {
      "serverUrl": "https://radar.creative-technology.digital/api/mcp/mcp"
    }
  }
}

Claude Code

  1. For project-level config, create or edit .mcp.json in your project root.
  2. For user-level config, edit ~/.claude.json.
  3. Add the mcpServers block below (merge with existing if present).
{
  "mcpServers": {
    "signal-radar": {
      "type": "http",
      "url": "https://radar.creative-technology.digital/api/mcp/mcp"
    }
  }
}

Cursor

  1. Open Cursor → Settings → MCP (or edit ~/.cursor/mcp.json directly).
  2. Add the mcpServers block below (merge with existing if present).
  3. Restart Cursor — the radar tools will appear in the MCP tools list.
{
  "mcpServers": {
    "signal-radar": {
      "url": "https://radar.creative-technology.digital/api/mcp/mcp"
    }
  }
}

Slack

Custom Integration

Custom setup guide. Use the MCP endpoint to query radar data from bots or workflows.

Endpoint: Send POST requests to the MCP endpoint at https://radar.creative-technology.digital/api/mcp/mcp

Example request payload:

{
  "method": "tools/list",
  "params": {}
}

Teams

Custom Integration

Custom setup guide. Connect via the MCP endpoint to surface Signal data in channels.

Endpoint: Send POST requests to the MCP endpoint at https://radar.creative-technology.digital/api/mcp/mcp

Example request payload:

{
  "method": "tools/list",
  "params": {}
}

Glean

Custom Integration

Custom setup guide. Use the MCP endpoint to index Signal data in your search instance.

Endpoint: Send POST requests to the MCP endpoint at https://radar.creative-technology.digital/api/mcp/mcp

Example request payload:

{
  "method": "resources/list",
  "params": {}
}

Tools Library

* required

search_tools

Search Tools

Search the agentic tools radar using semantic search. Returns tools matching the query with similarity scores.

Reference

querystring*

Natural language search query

limitnumber

Maximum results to return (default: 5)

Examples

  • Search for code review tools
  • Find IDE tools with strong governance

Try It Playground

Prompting Tips

Do

  • Use natural language queries that describe the capability you want.
  • Add a category or context when you want narrower results.

Don't

  • Do not use internal IDs when a plain-language query will do.
  • Do not ask for more results than you plan to review.

get_tool_details

Get Tool Details

Get detailed information about a specific tool including scores, dimensions, status, and history.

Reference

toolIdstring

Exact tool ID

toolNamestring

Tool name (case-insensitive)

Examples

  • Get details for Cursor

Try It Playground

Prompting Tips

Do

  • Prefer toolId when you already have the exact identifier.
  • Use toolName for a quick follow-up after a search result.

Don't

  • Do not provide both toolId and toolName unless you need a fallback.

compare_tools

Compare Tools

Compare 2-3 tools side by side across all dimensions. Highlights governance differences and key differentiators.

Reference

toolIdsstring*

Comma-separated tool IDs (2-3)

Examples

  • Compare Cursor and Copilot

Try It Playground

Prompting Tips

Do

  • Compare two or three tools at a time for readable output.
  • Use tool IDs returned from search_tools for exact matches.

Don't

  • Do not compare large groups of tools in a single request.
  • Do not mix unrelated categories unless that contrast is the point.

get_risky_tools

Get Risky Tools

Find tools with governance gaps, security concerns, or CAUTION or CRITICAL markers.

Reference

severityenum

Filter by risk severity

lowGovernanceOnlyboolean

Only tools with compliance below 13/20 threshold

limitnumber

Max results

Examples

  • Show critical-risk tools

Try It Playground

Prompting Tips

Do

  • Filter by severity when you need a short triage list.
  • Use lowGovernanceOnly when governance is your primary screening factor.

Don't

  • Do not treat an empty result as proof that all tools are equally safe.

get_trending_tools

Get Trending Tools

Find tools with recent rating changes. Filter by trend direction.

Reference

directionenum

Filter by trend direction

limitnumber

Max results

Examples

  • Show newly added tools

Try It Playground

get_recommendations

Get Recommendations

Get top-rated tool recommendations. Filter by category or status level.

Reference

categorystring

Filter by category name

statusFilterenum

Filter by maturity status

limitnumber

Max results

Examples

  • Recommend adopted coding assistants

Try It Playground

Prompting Tips

Do

  • Use category when you already know the workflow you are shopping for.
  • Use statusFilter to align results with your adoption appetite.

Don't

  • Do not rely on recommendations alone when governance concerns are material.

get_timeline_events

Get Timeline Events

Browse the industry timeline of major events in agentic developer tools.

Reference

typeenum

Filter by event type

minSignificancenumber

Minimum significance level (1-5)

limitnumber

Max events to return

querystring

Keyword filter on title or description

Examples

  • Show major product launches with significance 4 or higher

Try It Playground

Prompting Tips

Do

  • Use minSignificance to keep the timeline focused on major changes.
  • Add a query when you are tracking a specific company or theme.

Don't

  • Do not ask for the entire timeline when a smaller slice will answer the question.

get_tool_history

Get Tool History

Get the version history and score changes for a specific tool over time.

Reference

toolIdstring

Tool UUID

toolNamestring

Tool name (case-insensitive)

Examples

  • Show Cursor history

Try It Playground

Prompting Tips

Do

  • Use this after get_tool_details when you want change-over-time context.
  • Ask for history on a single tool at a time.

Don't

  • Do not expect comparison output here; use compare_tools for side-by-side analysis.

get_insights

Get Insights

Get radar-wide insights and statistics including tool counts, averages, and top tools.

Examples

  • Summarize the current radar

Try It Playground

Prompting Tips

Do

  • Use this when you want a quick snapshot of the whole radar.
  • Follow up with narrower tools when an aggregate number raises questions.

Don't

  • Do not expect detailed per-tool analysis in this aggregate view.

submit_tool

Submit Tool

Submit a new agentic developer tool for evaluation. Creates a GitHub issue.

Reference

toolstring*

Tool name

productUrlstring*

URL to the product page

quickTakestring*

Brief description or elevator pitch

Examples

  • Submit a new evaluation candidate

Try It Playground

Prompting Tips

Do

  • Provide a clear product URL and a concise quick take.
  • Use this when the tool is not already present in the radar.

Don't

  • Do not include sensitive data in the submission fields.
  • Do not use placeholder URLs for real submissions.

get_intel_sources

Get Intel Sources

Search the ai-intel source archive. Returns ingested AI market news.

Reference

querystring

Keyword filter on title or summary

categorystring

Filter by category

relevanceenum

Filter by relevance level

limitnumber

Max results

Examples

  • Find recent high-relevance coding assistant coverage

Try It Playground

Prompting Tips

Do

  • Use relevance to surface the most strategic items first.
  • Combine query and category when you need targeted market scans.

Don't

  • Do not use overly broad queries if you want only a few sources.

get_intel_briefings

Get Intel Briefings

Get recent weekly intelligence digests from the ai-intel pipeline.

Reference

limitnumber

Number of recent digests to return

Examples

  • Show the three latest weekly digests

Try It Playground

Prompting Tips

Do

  • Use a small limit when you want a concise weekly recap.
  • Use this when source-level detail is less important than synthesized themes.

Don't

  • Do not expect raw source snippets here; use get_intel_sources for that.

search_intel

Search Intel

Unified keyword search across the ai-intel source archive and weekly digests.

Reference

querystring*

Search query

limitnumber

Max results per category

Examples

  • Search intel for reasoning model launches

Try It Playground

Prompting Tips

Do

  • Use a focused phrase when you want sources and briefings on the same topic.
  • Start here when you are not sure whether to browse sources or digests.

Don't

  • Do not treat this as a substitute for tool-specific radar queries.

brief_radar

Brief Radar

Return the most recent weekly intelligence digest in markdown, or a specific archived week via 'YYYY-WXX' notation.

Reference

weekstring

Specific ISO week to retrieve (e.g. '2026-W18')

Examples

  • Brief me on the latest week
  • Fetch the 2026-W18 weekly digest

Try It Playground

Prompting Tips

Do

  • Ask for the latest week first; only specify 'week' when you need a known prior digest.
  • Use this to anchor longer responses with an authoritative weekly narrative.

Don't

  • Do not assume a draft briefing has been human-reviewed (look for the 'DRAFT' flag).

tool_history

Tool History (detailed)

Deep historical timeline for a single tool: rating timeline, per-dim deltas, cap timeline, narrative summary. Optional from/to date range.

Reference

toolIdstring

Exact tool ID

toolNamestring

Tool name (case-insensitive)

fromstring

Start date (YYYY-MM-DD)

tostring

End date (YYYY-MM-DD)

Examples

  • Tool history for Cursor
  • Tool history for Claude Code from 2026-01-01 to 2026-05-01

Try It Playground

Prompting Tips

Do

  • Use this when 'how did this tool change' matters more than 'what is its current state'.
  • Bound long windows with from/to to keep the narrative focused.

Don't

  • Do not pass both toolId and toolName — pick one.

compare_tools_detailed

Compare Tools (detailed)

Deep comparison: per-dim rationale snippets, win/loss tally, movement triggers, and suggested follow-up questions.

Reference

toolIdsstring*

Comma-separated tool IDs (2-3)

Examples

  • Deep compare Cursor and Claude Code
  • Detailed comparison of GitHub Copilot, Cursor, and Cline

Try It Playground

Prompting Tips

Do

  • Use this when you need procurement-grade detail with rationale and follow-ups.
  • Pair with whats_changed when you want trajectories alongside the snapshot view.

Don't

  • Do not use this when a quick 2-tool comparison would do; prefer compare_tools.

whats_changed

What's Changed

Return the 'what should I care about right now' view: promotions, demotions, top climbers/fallers, and tools that gained caps.

Reference

sincestring

Look back from this date (default: 7 days ago, YYYY-MM-DD)

Examples

  • What's changed this week
  • What's changed since 2026-04-01

Try It Playground

Prompting Tips

Do

  • Use this as a daily/weekly pulse check.
  • Pair with brief_radar for narrative context behind the changes.

Don't

  • Do not assume zero changes means nothing happened — the radar updates monthly.

list_caps

List Scoring Caps

Full catalog of scoring caps with affected dimensions, type, category, and which tools currently have them. Pass a 'tool' to scope.

Reference

toolstring

Optional tool slug or name to focus on

Examples

  • List all caps
  • Which caps are applied to Devin

Try It Playground

Prompting Tips

Do

  • Use this to understand why a tool is held back from a higher rating.
  • Cross-reference cap categories (security, capability, enterprise, trust, stability) when assessing risk.

Don't

  • Do not assume removable=temporary; some caps are conditional and need specific evidence.

How is this different from the website?

The website is the readable surface — radar charts, tool cards, briefing pages. The MCP is the same data, addressable by your LLM. Different jobs, same source of truth.

LLM-native
Claude, ChatGPT, and Cursor can call the radar like a function. No copy-paste, no scraping, no stale screenshots.
Scriptable
POST to one endpoint and you can build a CI gate, a Slack bot, a quarterly review draft — anything that can speak JSON-RPC.
Queryable
whats_changed, brief_radar, compare_tools_detailed — questions that took ten clicks on the site become a one-line prompt.

Discovery file: /mcp.json · Endpoint: https://radar.creative-technology.digital/api/mcp/mcp · No auth, no rate limits today.