bjoaquinc/mcp - MCP Implementation

[andrewpareles]

[bjoaquinc]

Wanted to add some thoughts related to improving MCP implementation before or after launch:

• Shoot a warning regarding too many tools (Cursor has a dialog popup if you add over 50 and some LLMs stop recognizing tools after 40)--Note that just adding the github and atlassian MCP servers already made me hit that limit
• 2 servers can have the same tool name. Might be better to add the serverName as a param rather than derive it from a toolName. Including serverName as part of the params for every mcp tool would be a good solution, then extract it from params later. (DONE) -- added a unique prefix before each toolName to make it unique
• Don’t disable a server that has an error. Turning it off and on should be allowed
• Improve error handling from server responses: Here are the standard error codes we can already start handling:

ErrorCode {
    // Standard JSON-RPC error codes
    ParseError = -32700,
    InvalidRequest = -32600,
    MethodNotFound = -32601,
    InvalidParams = -32602,
    InternalError = -32603
}

• Add a copy button to command so that devs can try running the mcp server in their terminal to debug if it errored out. Especially important since it isnt possible to copy the text in Void Settings
• Improve utilization of additional context from the MCP server since some MCPs rely heavily on these for their tools to function properly:
  • Include annotations support
  • Include prompt support
  • Include resource support
• Add control over which tools to keep/remove