Ntealan Apis Mcp Server

Created By
Levis0045a year ago
A modular, extensible Model Context Protocol (MCP) server for NTeALan REST APIs dictionaries and contributions. This project provides a unified interface for managing dictionary data, articles, and user contributions, and is designed for easy integration and extension.
Overview

What is Ntealan Apis Mcp Server?

Ntealan Apis Mcp Server is a modular and extensible server designed for managing dictionary data, articles, and user contributions through the Model Context Protocol (MCP).

How to use Ntealan Apis Mcp Server?

To use the server, clone the repository, install the required dependencies, and run the server using Python. The server can be accessed via the provided endpoint for resource actions.

Key features of Ntealan Apis Mcp Server?

  • Dictionary Management: Create, update, delete, and retrieve dictionaries and their metadata.
  • Article Management: Manage articles within dictionaries, including statistics and filtering.
  • Contribution Management: Track and manage user contributions to articles and dictionaries.
  • Extensible MCP Server: Easily add new resources and tools.
  • Async Support: Built on fastmcp and aiohttp for high performance.

Use cases of Ntealan Apis Mcp Server?

  1. Managing a comprehensive dictionary database.
  2. Facilitating user contributions to dictionary entries.
  3. Providing a unified interface for accessing dictionary-related data.

FAQ from Ntealan Apis Mcp Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol designed for managing and sharing model context data.

  • How can I contribute to the project?

You can contribute by following the guidelines in the CONTRIBUTION.md file in the repository.

  • Is there a Docker deployment option?

Yes, the server can be deployed using Docker for production environments.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Levis0045
Star
0
Language
Python
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