Nody

Created By
olympeioa year ago
Nody provides a powerful MCP Composer for creating and managing custom MCP servers. It enables you to personalize each tool's name and description to add context, helping agents use them with fewer tokens. It manages the configurations and secrets of MCP servers in one secure place, making it easier to deploy and scale your AI toolsets efficiently.
Overview

One MCP Server to TOOL them all!

Nody is a developer-first platform for managing and deploying Model Context Protocol (MCP) servers and toolsets. Nody technology maintains the tools collections in a knowledge graph. Nody clients exposing tools to your AI Agents request the knowledge graph to discover what tool should ben installed and exposed.

Nody provides a powerful MCP Composer for creating and managing custom MCP servers. It enables you to personalize each tool's name and description to add context, helping agents use them with fewer tokens. It manages the configurations and secrets of MCP servers in one secure place, making it easier to deploy and scale your AI toolsets efficiently.

Server Config

{
  "mcpServers": {
    "<Nody client name>": {
      "command": "npx",
      "args": [
        "-y",
        "@olympeio/nody-vmcp@latest"
      ],
      "env": {
        "NODY_CLIENT_ID": "<Nody client id>",
        "NODY_USER_KEY": "<your very own secret encryption key>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
olympeio
Star
-
Language
-
License
-
Category

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