I love the Fibery MCP connector. I am using it like this:
I use Fibery as an ordinary interactive user
Three user accounts, Peter, Claude, Codex
Claude Code & Chat GPT Codex integrated in VS Code
I assign stories and bugs to the three users
I instruct Code and Codex to work on their assigned stories
Anyone can update and re-assign stories
This is all good, but I am running into two issues:
Code and Codex cannot add comments to stories or bugs. Is this a legitimate limitation, or something else?
I would like Code and Codex to authenticate through MCP independently, using their user accounts. This way, the Activity Log would accurately reflect who made which changes in Fibery. When I tried this, the MCP connection stopped working.
I am currently a free user. In my old job, we had 20+ premium seats. I am reaching the point where I should upgrade to the €20/month plan. Do I need to buy seats for the agent users and mee too? That would be €60/month - a bit pricy for me.
So far MCP has not tools to create comments, it will be added soon
Could you explain it deeper? Do you use separate users for that? It is not clear.
Currently MCP works under existing user. In some future we do want to introduce Agents users, but right now there are no other ways. So if you really need to separate your work from agents work, purchasing additional users is the only way. You can try to experiment with Guests, but they are quite limited.
I log in to Fibery in the browser with the “Peter” account. I connect to Fibery using the “Codex” user through MCP from VS Code. This causes problems. If I use the same email for both, there are no problems.
The MCP connection gets corrupted somehow, and the AI agent can’t read or make changes in Fibery. I have to delete the connection and set it up again. That doesn’t always work, and sometimes I can only access a small subset of the MCP interface.
I also see problems if I try to authenticate with Code, and Codex at the same time. Same or different emails.
It seems like there is only one authentication on the system, and trying to have two separate ones causes problems.
I hope that’s more clear. LMK if I can clarify further. Thank you.
I now suspect a different root cause for the problems I’m having. What is the expiry time on the OAuth token used to connect to fibery.io via MCP? After more investigation, I found a second fibery MCP server that uses a long-lived API token that does not expire. Should I be using this MCP server instead?
Thank you and I understand. The server you recommend has broader functionality. Unfortunately, it times out. I believe this is caused by the OAuth token expiring. In theory, I could simply re-authenticate, but there is a bug in Codex that makes this very difficult: MCP OAuth reauth succeeds but active session still uses stale refresh token (invalid_grant) · Issue #14144 · openai/codex · GitHub. The bug means the Codex does not pick up the new credentials when I re-authenticate. The work-around requires restarting VS Code and dropping the current conversation. I can instruct Codex to retain a resume point for the conversation, but that is an extra step. All difficult and it interrupts work flow. I guess this will all be mitigated when the Codex bug is fixed.
OTOH, is there a way to extend the time before the fibery.io OAuth token expired?
