-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package upgrade #1
base: main
Are you sure you want to change the base?
Conversation
Your free trial has expired. To keep using Ellipsis, sign up at https://app.ellipsis.dev or contact us. |
Tried out your branch @calclavia. I see you don't have the full fix yet. I'm trying out MCP for the first time so have limited knowledge here so far. Here's what I'm seeing in mcp logs (if its of any help) - seems like server is not responding and Claude keeps retrying:
|
Yeah there are still some issues I haven't had the time to take a look - perhaps someone familiar with Linear API could help |
@@ -89,17 +89,17 @@ class RateLimiter { | |||
const startTime = Date.now(); | |||
const queuePosition = this.queue.length; | |||
|
|||
console.log(`[Linear API] Enqueueing request${operation ? ` for ${operation}` : ''} (Queue position: ${queuePosition})`); | |||
console.error(`[Linear API] Enqueueing request${operation ? ` for ${operation}` : ''} (Queue position: ${queuePosition})`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏻 I had to make these same adjustments locally to get the MCP Server working, you can't use console.log
in an MCP Server as the protocol itself use the stdout
so all debugging statements need to route through stdout-err
.
I made a very basic upgrade to at least it's compatible with the latest Claude Desktop, but it still has errors when trying to read from Linear, so it's not a full fix.