claude-code - 💡(How to fix) Fix [Feature Request] Allow flexible MCP server and custom connector setup in claude.ai (like Devin) [1 participants]

TL;DR

The team should consider requesting enhancements to claude.ai's custom connector configuration and MCP server setup to support multiple authentication methods and admin-controlled permissions.

Guidance

• Review the current authentication methods supported by claude.ai and identify potential alternatives (e.g., API keys, basic auth) that could be proposed as additional options.
• Investigate the current permissions model in claude.ai and determine if there are any existing settings or workarounds that could provide more flexibility for admins to control user permissions.
• Reach out to the claude.ai development team or support to submit feature requests for the desired enhancements, providing specific examples of the team's use cases and pain points.
• Consider using the Claude Code CLI as a temporary workaround for custom connector and MCP server configuration, given its greater flexibility.

Example

No code snippet is provided as the issue is focused on configuration and feature requests rather than code-level issues.

Notes

The solution to this issue relies on enhancements to the claude.ai platform, which may require coordination with the development team. The team should be prepared to provide detailed feedback and use cases to support their feature requests.

Recommendation

Apply workaround: The team should use the Claude Code CLI as a temporary solution for custom connector and MCP server configuration, while awaiting potential enhancements to the claude.ai platform. This allows the team to leverage the greater flexibility of the CLI while still using the claude.ai platform for other features.