← Back to Home

Documentation

Learn how to use the MCP Uplink Platform to connect your AI assistants to real-world tools.

Getting Started

The MCP Uplink Platform allows you to use Model Context Protocol (MCP) servers without hosting them yourself. We act as a secure proxy between your AI client (like Claude Desktop) and the MCP servers.

1. Get an API Key

First, you need an API key to authenticate your requests. Go to the API Keys dashboard to generate one.

2. Configure Your Client

Add the MCP server configuration to your client's config file. For Claude Desktop, this is usually located at:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Here is an example configuration for Slack:

{
  "mcpServers": {
    "slack": {
      "url": "https://mcp.provider.com/api/mcp/slack",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      },
      "env": {
        "SLACK_BOT_TOKEN": "xoxb-your-bot-token",
        "SLACK_TEAM_ID": "T123456"
      }
    }
  }
}

3. Security & Privacy

We take security seriously. Here is how we handle your data:

  • No Credential Storage: We do not store your Slack tokens, Stripe keys, or any other service credentials. They are passed in the request and used only for that session.
  • Isolated Execution: Each request runs in an isolated environment.
  • Usage Logging: We log metadata about requests (method, response time) for analytics, but not the content of the data.

Available MCP Servers

Check out our Catalog to see all available MCP servers and their specific configuration requirements.

Supported Integrations

  • Slack: Send messages, read channels, manage users.
  • GitHub: Manage repositories, issues, pull requests.
  • Stripe: Manage payments, customers, subscriptions.
  • Google Drive: Access and manage files.
  • PostgreSQL: Query and manage databases.

API Reference

If you are building a custom client, you can interact with our API directly.

Endpoint

POST /api/mcp/[provider_slug]

Headers

  • Authorization: Bearer YOUR_API_KEY
  • Content-Type: application/json

Body

{
  "method": "tools/list", // or tools/call, resources/list, etc.
  "params": { ... },
  "env": {
    "KEY": "VALUE"
  }
}