Admiral connection settings

Configure authentication, check the connection and explore available tools.

MCP Connect by Apideck

Admiral

Publisher not verified · idle

CONNECTION SETTINGS

Connect this server

https://api.meetadmiral.com/mcp

Not connected

Authentication & preferences

Scope: this browser tab only

Client setup →

Inspect before you call

Connect to discover tools, then select one to inspect its input schema. No tool runs automatically.

Agent → MCP tool → Provider API or service

Connection evidence

Publisher: Affiliation not verified
Setup evidence: Registry metadata only
Protocol connection: Not tested in this browser
Tool discovery: Not tested in this browser

Connection results apply only to this browser session. Tool discovery does not test tool execution or establish safety. Publisher affiliation is reviewed separately.

3 sources

Claude connector directory · 2026-10-24
Glama connectors · 2026-10-24
Official MCP Registry · 2026-10-24

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

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 ↗

Connection guides: setup fields, authentication and publisher evidence →