Connect Newsmind to your AI assistant. Same hosted MCP server for every client — only the config syntax differs.
Server URL:
https://api.newsmind.app/functions/v1/mcp
Auth: OAuth 2.1 with PKCE and dynamic client registration (RFC 7591). For clients that don't yet speak OAuth, use a personal access token (Authorization: Bearer nm_…) generated from your Newsmind account.
Transport: HTTP/SSE (Streamable HTTP). The server also exposes a REST adapter at /api/v1/* for OpenAPI-aware clients (see ChatGPT).
npx newsmind-mcp stdio bridge (on the roadmap).
https://api.newsmind.app/functions/v1/mcpTry it: open a new chat and ask "What feeds am I subscribed to in Newsmind?" — Claude will call the list_feeds tool and return your subscriptions.
Same OAuth flow as Claude.ai.
https://api.newsmind.app/functions/v1/mcpIf your version only supports stdio MCP servers, see stdio bridge fallback.
Cursor supports remote MCP servers, but its OAuth handling for newer flows is still maturing. Bearer-token is the safer path today.
Edit ~/.cursor/mcp.json (create it if missing):
{
"mcpServers": {
"newsmind": {
"url": "https://api.newsmind.app/functions/v1/mcp",
"headers": {
"Authorization": "Bearer nm_YOUR_TOKEN_HERE"
}
}
}
}
Restart Cursor. If the server registers but tools don't show up, your version may not yet support remote HTTP MCP — use the stdio bridge fallback.
In your VS Code settings.json:
{
"cline.mcpServers": {
"newsmind": {
"type": "sse",
"url": "https://api.newsmind.app/functions/v1/mcp",
"headers": {
"Authorization": "Bearer nm_YOUR_TOKEN_HERE"
}
}
}
}
Reload the window after editing.
Zed's "context servers" are MCP under the hood; HTTP support depends on your Zed version.
In Zed settings.json:
{
"context_servers": {
"newsmind": {
"url": "https://api.newsmind.app/functions/v1/mcp",
"headers": {
"Authorization": "Bearer nm_YOUR_TOKEN_HERE"
}
}
}
}
If your Zed only supports stdio context servers, use the stdio bridge fallback.
In ~/.continue/config.json:
{
"experimental": {
"modelContextProtocolServers": [
{
"transport": {
"type": "sse",
"url": "https://api.newsmind.app/functions/v1/mcp",
"headers": {
"Authorization": "Bearer nm_YOUR_TOKEN_HERE"
}
}
}
]
}
}
Newsmind ships an OpenAPI 3.1 spec at:
https://api.newsmind.app/functions/v1/mcp/api/v1/openapi.json
Once the official Newsmind Custom GPT is published in the GPT Store, this section will link to it directly. ChatGPT Plus subscribers can build their own Custom GPT against that spec in the meantime.
For clients that only support stdio MCP servers (older versions of Cursor, Zed, Continue, etc.), an npx newsmind-mcp wrapper that proxies stdio ↔ remote HTTP is on the roadmap. Until it ships, use a client that supports remote HTTP MCP (Claude.ai is the easiest on-ramp).
Once connected, your AI gets these 10 tools. You don't need to memorize them — Claude/etc. picks the right one based on what you ask.
| Tool | What it does |
|---|---|
list_feeds | Lists your subscriptions |
subscribe | Adds a feed by RSS URL |
unsubscribe | Removes a feed |
get_unread | Returns unread articles, optionally filtered by feed/time |
get_article | Returns full extracted article content |
mark_read | Marks one or more articles as read |
star_articles | Marks articles as starred |
search_articles | Full-text search across your feeds |
counts | Unread counts grouped by feed or day |
since_last_check | Resumable cursor — articles since you last asked |
OAuth flow fails / "Couldn't send tool approval" — usually transient on the client side. Reload the client and retry. If it persists, disconnect and reconnect the connector.
Bearer token returns 401 — your token may have been rotated. Generate a fresh one from your Newsmind account.
Bearer token returns 402 — your trial has expired. Start a Pro subscription.
Tools don't show up after configuring — your client may not yet support remote HTTP MCP servers with the auth flow you're using. Email support@newsmind.app with your client name and version.