OAuth 2.0
If your client speaks OAuth, point it at the endpoint with no credential and let it discover the rest. Alchemist implements the standard MCP discovery chain:registration_endpoint, so clients self-register — no pre-issued client ID is needed. Protected resource metadata follows RFC 9728.
OAuth authenticates you as an existing Alchemist user. Sign in once at app.askalchemist.com first, or the server returns 401 even after the flow completes.
API key
For clients without OAuth — and for headless or CI runs, where no browser is available for the sign-in step — send the key as a bearer token:Copy and Paste Config
Copy this into your MCP client’s config file. Replace
YOUR_KEY with your API key.Connection details
System prompt
Copy and Paste System Prompt
Paste this into your agent’s system prompt or instructions field.
STDIO transport (self-hosted)
If your client only supports STDIO, run the MCP server locally:Verifying the connection
Calllist_filter_options (zero arguments) to confirm the server is live: