Adonis MCP

Created By
7nohea year ago
An AdonisJS package for building remote MCP servers
Overview

what is Adonis MCP?

Adonis MCP is a package designed for the AdonisJS framework that provides support for the Model Context Protocol (MCP), enabling the easy building of remote MCP servers using Server-Sent Events (SSE).

how to use Adonis MCP?

To use Adonis MCP, install the package with the command node ace add @7nohe/adonis-mcp, configure the generated config/mcp.ts file, register routes in start/routes.ts, and start the server with npm run dev.

key features of Adonis MCP?

  • Easy integration with AdonisJS framework.
  • Support for Server-Sent Events (SSE).
  • Customizable server settings through configuration files.
  • Route registration for tools and prompts.

use cases of Adonis MCP?

  1. Building real-time applications that require server communication.
  2. Creating tools that utilize the Model Context Protocol for data handling.
  3. Developing applications that need to process messages in real-time.

FAQ from Adonis MCP?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol designed for managing and processing data in a structured way, allowing for efficient communication between servers and clients.

  • Is Adonis MCP free to use?

Yes! Adonis MCP is open-source and available under the MIT License.

  • How can I debug my MCP server?

You can debug your MCP server using the configuration file or the Inspector tool provided in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
7nohe
Star
1
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)

a day ago