MCP Tabnews MCP Server

A service that provides access to TabNews API data

Local serverstdioTypeScript

What is the MCP Tabnews MCP server?

If you already use MCP Tabnews, the mcp tabnews mcp server is the piece that lets your assistant work with it directly. A service that provides access to TabNews API data.

What the server does

This MCP server is also available on Smithery for direct integration.

  • Built with Model Context Protocol (MCP)
  • Type-safe with TypeScript and Zod schema validation
  • Native TypeScript support in Node.js without transpilation
  • Standard I/O transport for easy integration
  • Structured error handling

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • checkStatusTool — Check the status of the TabNews API
  • getContentsTool — Get contents from TabNews
  • getContentsByUserTool — Get contents from TabNews by user
  • getContentTool — Get a content with body from TabNews by user and slug
  • getContentChildrenTool — Get comments from TabNews by content
  • getAnalyticsUserCreatedTool — Get the analytics of a user created contents from TabNews
  • getAnalyticsRootContentPublishedTool — Get the analytics of a root content published from TabNews
  • getAnalyticsChildContentPublishedTool — Get the analytics of a child content published from TabNews
  • getRssFeedTool — Get the RSS feed from TabNews

Installation

@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Tabnews's toolset — checkStatusTool, getContentsTool, getContentsByUserTool and 6 more — is a fair guide to whether it matches your workflow. It is maintained by renant; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Tabnews.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
checkStatusToolCheck the status of the TabNews API.
getContentsToolGet contents from TabNews.
getContentsByUserToolGet contents from TabNews by user.
getContentToolGet a content with body from TabNews by user and slug.
getContentChildrenToolGet comments from TabNews by content.
getAnalyticsUserCreatedToolGet the analytics of a user created contents from TabNews.
getAnalyticsRootContentPublishedToolGet the analytics of a root content published from TabNews.
getAnalyticsChildContentPublishedToolGet the analytics of a child content published from TabNews.
getRssFeedToolGet the RSS feed from TabNews.

How to install the MCP Tabnews MCP server

{
  "mcpServers": {
    "tabnews": {
      "command": "npx",
      "args": ["-y", "@smithery/cli"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use MCP Tabnews to checkStatusTool.
  • Use MCP Tabnews to getContentsTool.
  • Use MCP Tabnews to getContentsByUserTool.

Frequently asked questions

It connects MCP Tabnews to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (checkStatusTool, getContentsTool, getContentsByUserTool, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Tabnews directly.