slackapi / slackapi/slack-skills-plugin
Send Message Input Form resource consumes agent context window, breaking tool discovery
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 132
- Forks
- 34
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 16
Description
Bug Description
The Send Message Input Form MCP resource (ui://send-message-input.html) shipped with the Slack MCP plugin contains an enormous inline React application (full HTML + JS bundle). When an AI agent fetches this resource to understand the MCP's capabilities, the sheer size of the response consumes the agent's entire context window, preventing it from ever successfully discovering or calling the actual tools (e.g. slack_send_message).
Impact
- The agent sees the resource descriptor and fetches it first, assuming it describes how to send messages
- The fetched HTML is a full React app bundle — far too large and not useful for programmatic tool invocation
- After processing this payload, the agent has no remaining context to discover or call the real MCP tools
- Net result: the Slack MCP integration is effectively non-functional out of the box
Steps to Reproduce
- Have the Slack MCP plugin enabled in Cursor IDE (default configuration)
- Ask the AI agent to send a Slack message
- The agent discovers the
Send Message Input Formresource viaresources/Send_Message_Input_Form.json - Agent fetches
ui://send-message-input.html, receives the massive HTML/JS payload - Agent gets stuck processing the UI form content and never successfully calls
slack_send_message
Expected Behavior
The agent should be able to discover and call slack_send_message (and other tools) without the resource consuming its context window.
Workaround
Manually delete the resource descriptor file from the local MCP metadata:
mcps/plugin-slack-slack/resources/Send_Message_Input_Form.json
After deletion, tool discovery works correctly and slack_send_message sends messages as expected.
Suggested Fix
- Remove the
Send Message Input Formresource from the default MCP descriptor set, or - Gate it behind a UI-only flag that agents skip during tool discovery, or
- Drastically reduce its size so it doesn't overwhelm the context window
Environment
- IDE: Cursor
- MCP Plugin: Slack (
plugin-slack-slack) - Resource:
ui://send-message-input.html(described inresources/Send_Message_Input_Form.json)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting resources/Send_Message_Input_Form.json and the referenced ui://send-message-input.html resource in the Slack MCP plugin. Reproduce the Cursor discovery flow and verify that removing or gating this resource lets the agent discover and call slack_send_message without exhausting its context window.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100