[algis-hn]

The auth problem you've hit is the exact use case for OAuth relay at the proxy layer - the proxy holds enterprise tokens and handles refresh independently, so each tool integration stays stateless and free of credential lifecycle complexity. The natural language to specific ID mapping (your channel_id example) is the genuinely harder piece, though semantic routing at the middleware layer helps: the proxy selects the right tool based on semantic matching, which reduces how often the LLM needs to reason about entity IDs directly. What's missing isn't MCP features - it's an opinionated middleware layer that decouples auth handling and semantic routing from individual tool implementations. Some open-source proxy projects are building exactly this, though enterprise connectors for Teams and Salesforce at scale are still thin.