checkStatusToolLABSCO SUMMARY
A community's feed, readable where you are working.
Reading a post, its comments and the author's other writing are separate calls, so an assistant can follow a discussion properly rather than summarising the headline.
What it is
A read-only integration with TabNews, the Brazilian developer community. It covers content and the comments under it, everything a given user has published, the platform's own analytics, and the feed.
What you get
- Content listed from TabNews, and a single post fetched with its body by user and slug
- The comment thread under a post
- Everything a named user has published
- Platform analytics: users created, root content published, and child content published
- The RSS feed
- An API status check, for telling a TabNews outage apart from a configuration problem
Requirements
Node v23 or newer. Clone and npm ci, then point your client at the entry file. No account and no key - everything it reads is public.
Setup effort
Build from source
USE CASES
01
Catching up on what is being discussed
List the current content and pull the full body of the one worth reading.
02
Reading the argument, not just the post
Fetch the comments under the content, which is usually where the disagreement is.
03
Following a particular writer
Ask for everything a user has published, then read the pieces that matter.
04
Checking how the platform is doing over time
Read the analytics for users created and for root and child content published.
05
Wiring it into something that polls
Take the RSS feed, and check the API status first so an empty result is diagnosed rather than assumed.
9 tools
Listed in project docs. Your client may show a different list.
getContentsToolgetContentsByUserToolgetContentToolgetContentChildrenToolgetAnalyticsUserCreatedToolgetAnalyticsRootContentPublishedToolgetAnalyticsChildContentPublishedToolgetRssFeedToolBEFORE YOU INSTALL
What to know first
Tools you get
9 tools named in the project's documentation.
Requires
node on PATH
INSTALLATION
Connect your client
MCP Clients
Cursor
Use Node.js v23 or later — the server runs src/index.ts directly (check with node -v)
CURSOR · TERMINAL
git clone https://github.com/renant/mcp-tabnews.git
cd mcp-tabnews
npm ciCURSOR · JSON
{
"mcpServers": {
"mcp-tabnews": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PROJECT>/src/index.ts"
]
}
}
}<YOUR_PATH_TO_PROJECT> is the absolute path of the mcp-tabnews folder you just cloned. Put the block in ~/.cursor/mcp.json (or Cursor Settings → MCP → Add new MCP server).
