MCP Auth Python SDK

Created By
mcp-autha year ago
🔐 Plug-and-play auth for Python MCP servers.
Overview

What is MCP Auth Python SDK?

MCP Auth Python SDK is a plug-and-play authentication solution designed for Python MCP servers, enabling easy integration with OAuth 2.1 and OpenID Connect providers.

How to use MCP Auth Python SDK?

To use the SDK, install it via pip with the command pip install mcpauth, and refer to the documentation for detailed setup instructions.

Key features of MCP Auth Python SDK?

  • Supports OAuth 2.1 and OpenID Connect for secure authentication.
  • Easy installation and setup for Python developers.
  • Compatibility with various OAuth providers.

Use cases of MCP Auth Python SDK?

  1. Integrating authentication for web applications using MCP servers.
  2. Simplifying the connection to multiple OAuth providers.
  3. Enhancing security for applications requiring user authentication.

FAQ from MCP Auth Python SDK?

  • Is my provider supported?

Check the MCP-compatible providers for a list of supported providers.

  • How do I install the SDK?

You can install it using pip: pip install mcpauth.

  • Where can I find the documentation?

The full documentation is available at MCP Auth documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mcp-auth
Star
14
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago