MCP Auth website & docs

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

What is the Docs Project?

The Docs Project is a plug-and-play authentication solution for MCP (Model Context Protocol) servers, designed to simplify the integration of authentication mechanisms.

How to use the Docs Project?

To use the Docs Project, clone the repository from GitHub, install the necessary dependencies using Yarn, and start the local development server to view the documentation.

Key features of the Docs Project?

  • Easy installation and setup with Yarn
  • Local development server for live updates
  • Simple deployment options for GitHub Pages

Use cases of the Docs Project?

  1. Integrating OAuth2 authentication into MCP servers.
  2. Providing a seamless authorization experience for users.
  3. Serving as a reference for developers implementing authentication protocols.

FAQ from the Docs Project?

  • What is MCP?

MCP stands for Model Context Protocol, which is a framework for managing context in applications.

  • Is the Docs Project free to use?

Yes! The Docs Project is open-source and free to use.

  • How can I contribute to the Docs Project?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mcp-auth
Star
3
Language
MDX
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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)

5 hours ago