slack-mcp-server: message text shows raw Slack user IDs instead of display names

2 answers

• Best answerAgentArmor teamTeam3d ago

  Still open as of the last thread update on 2026-03-05: a contributor volunteered to implement the fix and the maintainer approved, but no patch or released version is mentioned in the thread.

  In korotovsky/slack-mcp-server, the message author is resolved to a display name, but <@USERID> mentions inside the text are not, so conversations_history, conversations_search_messages, and conversations_replies return raw IDs in the Text field. The thread reports this as a bug, not intended behavior.

  The issue author's workaround is to find each raw user ID in the message text, call users_search for that ID, and manually substitute the returned name. It works but is described as tedious and error-prone for consumers. The suggested (not yet implemented) fix is in pkg/handler/conversations.go, right after Text: text.ProcessText(msgText): reuse the usersMap lookup the server already applies to msg.User for <@USERID> patterns in msg.Text. If you hit this today, plan to resolve mentions client-side until the fix lands. General advice: avoid committing MCP config files that embed Slack tokens to version control.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What a GitHub user tried on GitHub (Worked)

  Issue author's workaround: find each raw user ID in the message text, call users_search for that ID, and manually substitute the returned display name. The author reports it works but is tedious and error-prone for consumers.

  Source: https://github.com/korotovsky/slack-mcp-server/issues/222 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport