# MCP access from LIttlebird ai

**URL:** <https://forum.newsblur.com/t/mcp-access-from-littlebird-ai/13806>\
**Category:** problem\
**Created:** [August 20, 2026, 12:54pm UTC](https://forum.newsblur.com/t/mcp-access-from-littlebird-ai/13806 "2026-08-20T12:54:34Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![samuelclay](https://forum.newsblur.com/user_avatar/forum.newsblur.com/samuelclay/32/857_2.png) [@samuelclay](https://forum.newsblur.com/u/samuelclay)\
**Post date:** [October 29, 2026, 1:36pm UTC](https://forum.newsblur.com/t/mcp-access-from-littlebird-ai/13806/10 "2026-10-29T13:36:39Z")

</div>

I think I found it. Littlebird looks for our OAuth details at the root of [newsblur.com](http://newsblur.com), the way an older version of the MCP spec worked. We only published them under /mcp, so Littlebird never learned that NewsBlur uses OAuth. It skipped the browser sign in and called the server with no token, which is the “rejected the API token” error.

NewsBlur now publishes those details in both places. There’s no API token to find, MCP only uses the OAuth sign in. Remove the server in Littlebird and add [https://newsblur.com/mcp](https://newsblur.com/mcp) again, with or without the trailing slash. Your earlier screenshot had https:/newsblur.com/mcp/ with a single slash, so make sure it starts with https:// this time. It should then open a browser window to approve access. If it still fails, tell me exactly what it says and I’ll keep digging.

---

_[View the full topic](https://forum.newsblur.com/t/mcp-access-from-littlebird-ai/13806)._