[Feature Request] Allow flexible MCP server and custom connector setup in claude.ai (like Devin)

Summary

We are a team using claude.ai with Slack integration for daily development work. We have several pain points around MCP server and custom connector configuration in claude.ai.

Feedback

1. Custom connector setup is too restrictive (OAuth-only)

Currently, adding custom connectors only supports OAuth authentication, which makes it very difficult to integrate with many internal tools. Supporting other auth methods (API keys, basic auth, etc.) would greatly improve usability.

2. Allow any MCP server (remote or local) to be configured freely

Similar to how Devin allows users to set up any MCP server regardless of whether it's remote or local, we'd like the same flexibility in claude.ai. Currently the options are very limited compared to Claude Code CLI.

3. Admin-controlled permissions for users to add custom connectors/MCPs

We'd like a model where:

• Organization admins can allow individual users to add their own custom connectors and MCP servers
• Users can freely configure integrations within the permissions granted by their admin
• This would reduce the bottleneck on admins while maintaining control

Context

These limitations are the biggest friction point for our team adopting claude.ai's Slack integration for development workflows. The Claude Code CLI is much more flexible in this regard, and we'd love to see that flexibility extended to the claude.ai platform.

Environment

• claude.ai with Slack integration
• Team of ~5 engineers