Why am I having to reauthenticatw the pocket MCP EVERY SINGLE DAY? That rather defeats the purpose of it.
Its setup. It’s authenticated. It works. I can have Claude do stuff. And then tomorrow it fails and I have to reauthenticate. Again. Several days running. So you functionally don’t have an MCP interface right now.
Edit to add - tried it on my desktop. Checked Connectors. Pocket is connected. Ran command. Fail. Pocket isn’t connected. Tried again. Failed. Told to disconnect / reconnect. Did that. It worked. So it wasn’t connected.
Whoever wrote this piece needs firing, right now. You are not competent to be in charge of our data. This is ridiculous. If you don’t want to offer a feature, don’t offer it. But if you offer it - Do It Properly. This is intern level garbage.
Hey, sorry about that. We dug into this and it turns out Claude doesn’t auto-refresh MCP OAuth tokens when they expire, so it drops the connection and makes you re-login. This affects basically every MCP server on Claude. There are open issues with Anthropic to fix it on their end.
We went ahead and shipped a fix on ours though, so once Anthropic patches their client it’ll just stay connected. In the meantime you should see way less reauthentication. Let us know how it goes!
Ok…. Except none of my other connectors do that. Are you oauth and they aren’t? Or…?
how about a perplexity connector so we can do a/b testing?