Samva MCP

MCP detected

Details

Endpoint: https://mcp.samva.dev
Transport: streamable-http
Docs: https://samva.dev/docs/developers/mcp

Authentication

OAuth 2.0 oauth2 detected

OAuth · resolves from well-known metadata

OAuth 2.0 — self-onboarding

Point your MCP client at the server URL and approve access in the browser. The server accepts a Client ID Metadata Document (CIMD), so the client authenticates with its own hosted URL as the client_id — nothing to register.

Samva API key api_key declared Get key ↗

X-API-Key: <credential>

In the Samva dashboard, open Developers → API Keys and create a key. Copy it when shown — the full value is only displayed once. Production keys start with samva_sk_live_ and test keys with samva_sk_test_. Store it in SAMVA_API_KEY and send it as X-API-Key on HTTP requests; some docs also show it accepted as Authorization: Bearer <api-key> on the hosted MCP server.