Ever Works Directory Website Template

Created By
ever-worksa year ago
A curated list of the best MCP Servers, featuring top solutions, libraries, tools, and more. -
Overview

What is Ever Works Directory Website Template?

The Ever Works Directory Website Template is a full-stack directory website solution built with Next.js 15, designed to showcase the best MCP servers along with top solutions, libraries, and tools.

How to use Ever Works Directory Website Template?

To use this template, clone the repository from GitHub, set up your environment variables, and run the application locally or deploy it on Vercel.

Key features of Ever Works Directory Website Template?

  • Built with Next.js 15 for modern web applications
  • Supports multiple databases including PostgreSQL and MySQL
  • Git-based content management system for easy content updates
  • Internationalization support for multiple languages
  • Authentication options including OAuth providers like Google and GitHub

Use cases of Ever Works Directory Website Template?

  1. Creating a directory for MCP servers and related tools.
  2. Building a blog or content site with a structured content management system.
  3. Developing a customizable web application with user authentication.

FAQ from Ever Works Directory Website Template?

  • Is this template free to use?

Yes! The Ever Works Directory Website Template is open-source and free to use.

  • What technologies are used in this template?

The template uses TypeScript, Node.js, Next.js, and Tailwind CSS among others.

  • How can I contribute to the project?

You can contribute by submitting feature requests or pull requests on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ever-works
Star
2
Language
TypeScript
License
AGPL-3.0 license

Recommend Servers

View All
Alloy

2 days 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)

8 hours ago
Crevio

a day ago