bug(mcp): MCP session token expries after 1 day, forcing re-auth and breaking multi-day workflows
Open
Nobody has claimed this yet.
bug
feature/mcp
team/posthog-ai
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Bug Description
Day-to-day session timeouts are annoying. As a user, if I spread research across a couple of days, the connection is broken when I come back. I have to re-authenticate the MCP and start a new Claude session. Very disruptive when you're trying to keep context on a deeper analysis.
How to reproduce
- Start convo with Claude
- Use the PostHog MCP (authenticated)
- Wait ~1 days
- Continue conversation
Additional context
https://posthog.slack.com/archives/C075EH38BR8/p1776875887512939
Debug info
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by reproducing the authenticated PostHog MCP workflow with Claude and inspect where the one-day session expiration is enforced; done means a multi-day conversation can continue without re-authentication or losing its MCP connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100