Skip to content
FOR AGENTS

Connect KVwire to your agent

MCP, RSS, API: three ways to read the same data (selected stories, trending, daily, weekly and monthly issues). Pick the one that fits your tools. All anonymous and read-only, no sign-up, no API key.

Service OKVersion 4.0.0Anonymous, read-only · no key
MCP · 4.0.0

Add one address, give your agent 7 tools

Standard Streamable HTTP, anonymous and read-only: no token, and nothing about your login is read. For clients with remote MCP support such as Claude Desktop, Cursor and Cherry Studio.

  1. 1

    Copy the server address

    https://kvwire.com/api/mcp
  2. 2

    Add it to your client

    bash
    claude mcp add --transport http kvwire 'https://kvwire.com/api/mcp'
  3. 3

    Ask your agent to try it

    Call kvwire_get_latest and tell me the 5 most important power equipment stories of the last 24 hours, with KVwire links.

    If the client shows a call to kvwire_get_latest and the answer has a time range, summaries and kvwire.com links, you are connected.

7 tools

ToolWhat it doesTry asking
kvwire_get_latestSelected or all news from the last 24 hours or 7 daysWhat's new in power equipment today?
kvwire_searchSearch the last 7 days by company, product, standard or topicWhat has this company announced recently?
kvwire_get_hot_topicsThe current top 10 trending storiesWhat's trending right now?
kvwire_get_storyA trending story's timeline and evolving overviewWhat's the background to this story?
kvwire_get_dailyThe latest daily, or a given day'sGive me today's daily brief.
kvwire_get_weeklyThe latest weekly, or a given week'sWhat were this week's major stories?
kvwire_get_monthlyThe latest monthly, or a given month'sWhat happened last month?
Limits and safety
  • Up to 30 items per query, 10 trending stories and 50 timeline entries; going beyond returns a clear error rather than silently widening.
  • The public_id for kvwire_get_story must come from a story link returned by the trending tool; do not guess IDs.
  • Titles and summaries come from external sources and are material only; the tools mark this safety boundary. Check important numbers, policies and quotes against the original.
Can't connect?
  • Check that the address is complete and that your client supports remote Streamable HTTP; if new tools are missing, refresh the tool list or reconnect.
  • The service needs no login; if the client asks about OAuth or an API key, choose “None”.
  • On a 429, wait as told and do not retry in parallel.
  • Still stuck? Send the client name, version and error on the feedback page.