API Tracker / MCP servers / MCP Connect ← Back to connection options MCP Connect by Apideck
Host setup required Add the remote server, sign in to Vellm and review permissions. The public setup page does not specify the authentication protocol; follow publisher instructions. Publisher sources reviewed; no authenticated runtime test performed.
Publisher setup documentation →
2 sources Source-declared authentication: unknown. Publisher affiliation and successful connection are not inferred.
01 Choose your connections Search the cloud catalog across registries.
Catalog coverage Search MCPs SourceAll sources Glama remote connectors Glama source-code catalog Official MCP Registry API Tracker reviewed presets PublisherAll publishers Official only
Searching the cloud catalog…
02 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": {}
}Copy configuration Download
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 ↗ Connection guides: setup fields, authentication and publisher evidence →
Upcoming · by Apideck MCP connectivity, batteries included. Discovery, connection UI, tool access and activity views for your product. You bring the model and own credential storage.
Discover Browse the MCP catalog
Connect Review connection settings
Use tools Explore tools and chat Inspect Follow calls and activity SDK launch upcoming. The repository is currently private.
