MCP.so
ログイン

Wikipedia MCP Server

@1999AZZAR

Wikipedia MCP Server について

Minimal TypeScript-based HTTP server exposing Wikipedia search and page retrieval via MediaWiki API

基本情報

カテゴリ

その他

ランタイム

node

トランスポート

stdio

公開者

1999AZZAR

設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Wikipedia MCP Server?

A minimal TypeScript-based HTTP server that exposes Wikipedia search and page retrieval via the MediaWiki API. It features configurable caching, security headers, CORS, rate limiting, and supports REST, GraphQL, and JSON-RPC interfaces.

How to use Wikipedia MCP Server?

Clone the repository, copy .env.example to .env, install dependencies (npm install), build (npm run build), and start the server (npm run start). By default it listens on port 3000. Configure via environment variables in .env. Access the interactive Swagger UI at /docs.

Key features of Wikipedia MCP Server

  • Search articles via GET /search with optional title filtering.
  • Retrieve parsed HTML and sections by page title or page ID.
  • Configurable LRU cache (CACHE_MAX, CACHE_TTL).
  • Rate limiting by IP+endpoint (RATE_LIMIT_WINDOW, RATE_LIMIT_MAX).
  • Health and readiness endpoints (/health, /ready).
  • GraphQL endpoint at /graphql with interactive playground.

Use cases of Wikipedia MCP Server

  • Integrate Wikipedia search and content retrieval into your application.
  • Build a custom frontend that displays parsed Wikipedia articles.
  • Automate fetching of Wikipedia page data for analysis or archiving.
  • Use as a lightweight microservice for AI or chatbot context gathering.

FAQ from Wikipedia MCP Server

What are the runtime requirements?

Node.js v14 or later and npm.

How do I configure the server?

Create a .env file with variables like PORT, CACHE_MAX, CACHE_TTL, RATE_LIMIT_WINDOW, RATE_LIMIT_MAX, and ALLOWED_ORIGINS. Defaults are provided.

What transports can I use?

REST over HTTP, GraphQL (at /graphql), and JSON-RPC via stdin/stdout using the included transport classes.

Does it support authentication?

No authentication or API keys are mentioned; the server is designed for local or trusted-network use, with optional CORS control.

What caching is available?

An LRU cache with configurable max entries (CACHE_MAX, default 100) and TTL (CACHE_TTL, default 300000 ms) to speed up repeated requests.

コメント

「その他」の他のコンテンツ