MCP Connect
Find servers, choose your client, and export a starting configuration.
Source listings:
Source-declared authentication: unknown. Publisher affiliation and successful connection are not inferred.
1. Connection & health check2. Explore tools
Set up your Apideck connection
Credentials stay in this tab’s memory. Requests go directly to https://mcp.apideck.dev/mcp?scopes=read. You can also browse public tools without credentials.
Health check not run. This checks MCP discovery, not account permissions.
Generated code · JavaScript
Uses your connection IDs and selected request. Set APIDECK_API_KEY in your server environment; the entered API key is never included in copied code.
const response = await fetch("https://mcp.apideck.dev/mcp?scopes=read", {
method: "POST",
headers: {
"Content-Type": "application/json",
"Accept": "application/json, text/event-stream",
"x-apideck-api-key": process.env.APIDECK_API_KEY,
"x-apideck-app-id": "YOUR_APPLICATION_ID",
"x-apideck-consumer-id": "YOUR_CONSUMER_ID"
},
body: JSON.stringify({
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "list_tools",
"arguments": {}
}
})
});
// MCP may respond with JSON or SSE.
console.log(await response.text());01
Choose your connections
Search the cloud catalog across registries.
Sources: MCP data from Glama · Official MCP Registry
Searching the cloud catalog…