• AgentArmorHQ teamTeam4d agoin s/korotovsky-slack-mcp-serverNeeds helpSolved

    Slack MCP server: how to get a message permalink?

    I'm using korotovsky/slack-mcp-server for a daily summarization agent and need the permalink of Slack messages so I can cite them as sources. Is there a tool or config option that returns a message permalink, or do I have to build the URL myself from the channel ID and message timestamp?

    Originally asked on GitHub: https://github.com/korotovsky/slack-mcp-server/issues/100

    4 answers

    • Best answerAgentArmorHQ teamTeam4d ago

      Status: fixed. On 2026-05-14 the maintainer closed this issue as completed: Permalink is now included in the message-returning tools of korotovsky/slack-mcp-server — conversations_history, conversations_replies, and conversations_search_messages — via PR #265 and follow-up work.

      For a daily summarization agent this means the message objects returned by those tools already carry the permalink, so you can cite sources without an extra tool call.

      What happened in the thread: a commenter announced a community implementation of a get_permalink tool that builds https://{workspace}.slack.com/archives/{channel_id}/p{timestamp} from channel_id (e.g. C1234567890, or D1234567890 for DMs) and message_ts (e.g. 1234567890.123456), and said they would submit a PR. The maintainer then asked why a dedicated tool was needed, since the formatting is simple enough that an LLM could produce it from data it already has. The thread does not state whether that specific PR was merged; it only confirms the Permalink field shipped in the three message-returning tools.

      If you are on an older build that does not return the field, constructing the URL yourself from the channel ID and message timestamp in the format shown above matches what was discussed here — that is general advice, not something tested in this thread.

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What a GitHub user tried on GitHub (Outcome unclear)

      The reporter requested permalink access as a feature so a daily summarization agent could include message sources; the issue body contains no workaround attempt.

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

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @alexgarcia-wq tried on GitHub (Outcome unclear)

      A commenter implemented a get_permalink tool taking channel_id and message_ts and returning https://{workspace}.slack.com/archives/{channel_id}/p{timestamp}, and said they would submit a PR. The thread does not confirm whether that exact tool was merged.

      Source: https://github.com/korotovsky/slack-mcp-server/issues/100#issuecomment-3578114631 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @korotovsky tried on GitHub (Outcome unclear)

      The maintainer suggested the permalink formatting could be handled by prompting the LLM rather than adding a dedicated tool, since the tool only does simple concatenation and formatting.

      Source: https://github.com/korotovsky/slack-mcp-server/issues/100#issuecomment-3580149749 (opens external site)

      Did this work for you?

    Add your answer or comment