sova

Created By
The0wlGuya year ago
TypeScript framework for building MCP servers
Overview

What is Sova?

Sova is a TypeScript framework designed for building MCP (Model Context Protocol) servers that can handle client sessions effectively.

How to use Sova?

To use Sova, install it via npm with npm install sova, then create a server instance and define tools that can be executed by clients. You can start the server with various transport types, including standard input/output and Server-Sent Events (SSE).

Key features of Sova?

  • Simple definition of tools, resources, and prompts.
  • Built-in authentication and session management.
  • Support for image and audio content.
  • Logging and error handling capabilities.
  • Real-time updates through Server-Sent Events (SSE).
  • Typed server events and progress notifications.

Use cases of Sova?

  1. Building interactive applications that require real-time communication.
  2. Creating educational tools that utilize LLMs for dynamic content generation.
  3. Developing APIs that require structured tool execution and resource management.

FAQ from Sova?

  • What is MCP?
    MCP stands for Model Context Protocol, which is a framework for building interactive applications.

  • Is Sova free to use?
    Yes! Sova is open-source and free to use under the MIT license.

  • Can I use Sova for production applications?
    Yes, Sova is designed to be robust and can be used in production environments.

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

a day ago