Dictionary Server

Created By
meowraina year ago
Overview

what is Dictionary Server?

Dictionary Server is a dictionary server that supports the Model Context Protocol (MCP), allowing integration with AI assistants like Claude.

how to use Dictionary Server?

To use the Dictionary Server, install the dependencies, build the server, and start it using the provided npm commands. You can also test it using the MCP Inspector.

key features of Dictionary Server?

  • Integration with AI assistants via MCP protocol
  • Dictionary query tool for word lookup

use cases of Dictionary Server?

  1. Providing definitions and examples for words in applications.
  2. Enhancing AI assistants with dictionary capabilities.
  3. Supporting language learning tools with word lookup features.

FAQ from Dictionary Server?

  • What is the MCP protocol?

The MCP protocol is a communication protocol that allows different AI systems to interact with each other.

  • How do I install the Dictionary Server?

You can install it by running npm install in your terminal.

  • Can I use this server for multiple languages?

Yes, the server can be configured to support multiple languages depending on the dictionary data provided.

Server Config

{
  "mcpServers": {
    "dictionary-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-dictionary"
      ],
      "disabled": false
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
meowrain
Star
-
Language
-
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