MCP Server Auth Template

What this does

MCP Server Auth Template exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server declares the following environment variables. Set only the ones the maker requires for your setup; this listing does not flag any of them as required:

MCP_SERVER_RESOURCE_SERVER_URL
MCP_SERVER_AUTH_PROVIDER
MCP_SERVER_REQUIRED_SCOPES
MCP_SERVER_TRANSPORT_ALLOWED_HOSTS
MCP_SERVER_ENTRA_TENANT_ID
MCP_SERVER_ENTRA_AUDIENCE
MCP_SERVER_ENTRA_APPLICATION_ID_URI
MCP_SERVER_GENERIC_ISSUER_URL
MCP_SERVER_GENERIC_AUDIENCE
MCP_SERVER_GENERIC_JWKS_ALLOWED_ORIGINS

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install MCP Server Auth Template?

The install section on this page carries the maker's install command for MCP Server Auth Template, as submitted. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with MCP Server Auth Template?

This page carries setup and config for Claude Code. Any other MCP client that accepts a standard server config can connect to MCP Server Auth Template as well.

Does MCP Server Auth Template need an API key?

This listing does not flag an API key as required. The server can use these environment variables: MCP_SERVER_RESOURCE_SERVER_URL, MCP_SERVER_AUTH_PROVIDER, MCP_SERVER_REQUIRED_SCOPES, MCP_SERVER_TRANSPORT_ALLOWED_HOSTS, MCP_SERVER_ENTRA_TENANT_ID, MCP_SERVER_ENTRA_AUDIENCE, MCP_SERVER_ENTRA_APPLICATION_ID_URI, MCP_SERVER_GENERIC_ISSUER_URL, MCP_SERVER_GENERIC_AUDIENCE, MCP_SERVER_GENERIC_JWKS_ALLOWED_ORIGINS; the maker's docs say which of them your setup needs. They go in the env block of your MCP config.