Provides tools for interacting with Slack, enabling AI agents to list channels and send messages through a secure, hosted MCP proxy.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Uplink Connect to my Slack server and only enable the send_message tool"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
The official CLI for MCP Uplink - Cloud MCP Hosting for AI Agents
Your AI Agents: Faster, Cheaper, Safer
Connect Claude Desktop, Cursor, VS Code, Windsurf and any MCP-compatible AI client to the MCP Uplink cloud platform.
Problem | Solution |
š„ Too many tokens | Only load the tools you need. Reduce context by 60%. |
šø High API costs | Fewer tokens = lower costs. Calculate savings at mcp-calculator |
š¤ LLM hallucinations | Less noise = more accurate responses. Specialized agents perform better. |
š Security concerns | Zero Trust: Your credentials NEVER leave your machine. |
āļø Infrastructure headaches | We manage MCP servers. You focus on building. |
Related MCP server: mcp-compressor
Reduce your context window by only exposing the tools your agent actually needs.
ā Native MCP: Sends ALL 50+ tool definitions ā Heavy load, confused LLM
ā
MCP Uplink: Only sends 5 tools you need ā Fast, focused, accurateResult: 60% less tokens, fewer hallucinations, better responses.
Layer 1: Zero Trust Architecture
Your API keys and tokens stay in YOUR local .env file
Secrets are transmitted in-memory via encrypted HTTPS headers
We NEVER store your credentials - we're just a secure proxy
Layer 2: Tool Blocking
Block dangerous tools like delete, drop, modify
Prevent catastrophic accidents where an agent deletes your database
Less noise = faster and more accurate LLM responses
Agents respond instantly with higher quality answers
Managed infrastructure = no DevOps overhead for you
No installation required! Just use npx:
npx mcp-uplink connect --url https://mcp-uplink.com/api/mcp/slackOr install globally for faster startup:
npm install -g mcp-uplinkAdd this to your claude_desktop_config.json:
OS | Path |
Mac |
|
Windows |
|
Linux |
|
{
"mcpServers": {
"slack": {
"command": "npx",
"args": [
"-y",
"mcp-uplink",
"connect",
"--url", "https://mcp-uplink.com/api/mcp/slack"
],
"env": {
"MCP_API_KEY": "your-mcp-uplink-api-key",
"MCP_ENABLED_TOOLS": "send_message,list_channels",
"SLACK_BOT_TOKEN": "xoxb-your-slack-token",
"SLACK_TEAM_ID": "T0123456789"
}
}
}
}Same configuration format - just add to your MCP settings.
Option | Description |
| Required. MCP Uplink endpoint URL |
| Platform API key (or set |
| Comma-separated list of tools to enable |
| Disable environment variable forwarding |
| Only forward env vars with this prefix |
Variable | Description |
| Your MCP Uplink API key |
| Tools to enable (e.g., |
| Default server URL |
| Prefix filter for env vars |
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā YOUR MACHINE (Secure) ā
ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā ā
ā ā .env file ā ā
ā ā SLACK_BOT_TOKEN=xoxb-xxx (never leaves here) ā ā
ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā ā
ā ā ā
ā ā¼ ā
ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā ā
ā ā mcp-uplink CLI (local process) ā ā
ā ā - Captures env vars in-memory ā ā
ā ā - Encrypts via HTTPS header (X-Mcp-Env) ā ā
ā āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā
ā¼ HTTPS (encrypted)
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā MCP UPLINK CLOUD ā
ā - Receives request ā
ā - Decrypts env vars IN-MEMORY ONLY ā
ā - Executes MCP tool ā
ā - Immediately forgets credentials (no storage) ā
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāKey Security Features:
ā Ephemeral Secrets: Never stored, only used in-memory
ā HTTPS Transport: All data encrypted in transit
ā Blacklist Filtering: System vars (PATH, SHELL) are never forwarded
ā Tool Blocking: Prevent dangerous operations
sequenceDiagram
participant Claude as Claude Desktop
participant Bridge as mcp-uplink (local)
participant Cloud as MCP Uplink Cloud
participant MCP as MCP Server
Claude->>Bridge: tools/list
Bridge->>Cloud: POST /api/mcp/slack (+ X-Mcp-Env header)
Cloud->>MCP: Execute with filtered tools
MCP-->>Cloud: Tool definitions
Cloud-->>Bridge: Filtered response
Bridge-->>Claude: Only enabled toolsWebsite: https://mcp-uplink.com
Cost Calculator: https://mcp-uplink.com/mcp-calculator
MCP Marketplace: https://mcp-uplink.com/marketplace
Documentation: https://mcp-uplink.com/docs
MIT Ā© MCP Uplink
This server cannot be deployed
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
A registry of AI agent tools ā MCP servers, APIs, CLIs, SDKs ā kept current by automated ingestion.
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows