feat: add and export error types for MCP

[utkarsh-dixit]

TL;DR

Added specialized MCP error classes to improve error handling and provide more specific error types for MCP operations.

What changed?

• Created a new file McpErrors.ts with specialized error classes for MCP operations:
  • McpInvalidInputError: For invalid input validation
  • McpServerExistsError: When attempting to create a server that already exists
  • McpServerNotFoundError: When a requested server is not found
  • McpOperationFailedError: When an MCP operation fails
  • McpParsingFailedError: When response parsing fails
  • McpConfigNotFoundError: When a configuration is not found
  • McpUnauthorizedError: When unauthorized access is attempted
• Added error code constants in MCP_ERROR_CODES
• Exported all new error classes in the main index.ts
• Replaced generic ValidationError instances in the MCP class with the appropriate specialized error classes

How to test?

1. Try various MCP operations with invalid inputs or edge cases
2. Verify that the appropriate error classes are thrown
3. Test error handling with try/catch blocks using instanceof checks:

try {
  await composio.mcp.create('', []);
} catch (error) {
  if (error instanceof McpInvalidInputError) {
    console.log('Invalid input provided');
  }
}

Why make this change?

This change improves error handling by providing more specific error types for MCP operations. This allows consumers of the SDK to:

• Catch and handle specific error types more precisely
• Implement better error recovery strategies based on error type
• Get more descriptive error messages with appropriate error codes
• Improve type safety with the McpError union type for type checking

[utkarsh-dixit]

• feat: add and export error types for MCP #1755 👈 (View in Graphite)
• next

This stack of pull requests is managed by Graphite. Learn more about stacking.