MCP Connect

Find servers, choose your client, and export a starting configuration.

Connection guides: setup fields, authentication and publisher evidence →

MCP Connect by Apideck

Source listings:

Claude connector directory · 2026-10-24
API Tracker · publisher documentation · 2026-10-26

Source-declared authentication: oauth2. Publisher affiliation and successful connection are not inferred.

Host setup required

Register a Slack app with a fixed app ID and configure confidential OAuth with your client ID and client secret. Only Slack Marketplace-published or internal apps may use MCP; unlisted apps are not supported. Dynamic client registration and SSE are not supported. Each user authorizes the required scopes; workspace administrators may need to approve the app. Runtime access has not been tested.

Publisher setup documentation →

MCP Connect by ApideckYour setup · 0 selected ↓

Choose your connections

Search the cloud catalog across registries.

Catalog coverage

Search MCPsSourcePublisher

Searching the cloud catalog…

Your agent’s setup

0 servers selected

Build your tool stack

Add servers from the catalog. Your configuration appears here.

Choose your editor

VS Code.vscode/mcp.json

{
  "servers": {}
}

Merge this configuration into .vscode/mcp.json.
Open VS Code and start each server from its MCP settings.
Complete the publisher’s authentication flow if prompted.

Selection does not connect an account. Authentication and tool execution happen in your client. Some servers require additional setup from their publisher.

VS Code setup guide ↗