MCP Server com SSE e Autenticação Bearer

Created By
br-silvanoa year ago
MCP Server com SSE e Autenticação Bearer
Overview

What is MCP Server com SSE e Autenticação Bearer?

MCP Server com SSE e Autenticação Bearer is an implementation of a Model Context Protocol (MCP) server built in TypeScript. It utilizes Server-Sent Events (SSE) for real-time message transport and Bearer Token authentication, enabling secure communication with clients such as LLM hosts.

How to use MCP Server?

To use the MCP Server, clone the repository, install the dependencies, configure the Bearer Token in a .env file, and run the server using ts-node for development or compile it for production.

Key features of MCP Server?

  • Real-time communication using Server-Sent Events (SSE).
  • Secure authentication via Bearer Token.
  • Modular architecture following SOLID principles.
  • Example tool for basic arithmetic operations.
  • Direct execution of TypeScript files without pre-compilation.

Use cases of MCP Server?

  1. Real-time data communication for applications requiring instant updates.
  2. Secure API interactions with Bearer Token authentication.
  3. Integration with LLMs for enhanced functionality.

FAQ from MCP Server?

  • What is the purpose of the Bearer Token?

The Bearer Token is used to authenticate requests to ensure secure access to the server.

  • Can I run this server in production?

Yes, the server can be compiled and run in a production environment after building the TypeScript files.

  • What are the requirements to run this project?

You need Node.js (version 20 or higher), npm, TypeScript, and ts-node for development.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
br-silvano
Star
0
Language
TypeScript
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)

2 days ago