MCP-Wikipedia-API-Server

Created By
Rishavv007a year ago
A FastAPI-MCP server that fetches Wikipedia summaries for AI assistants, deployed using Google Colab and Ngrok.
Overview

what is MCP-Wikipedia-API-Server?

MCP-Wikipedia-API-Server is a FastAPI-based server that fetches Wikipedia summaries for AI assistants, enabling them to provide quick and relevant information.

how to use MCP-Wikipedia-API-Server?

To use the server, deploy it on Google Colab, authenticate Ngrok, and then send queries to fetch Wikipedia summaries.

key features of MCP-Wikipedia-API-Server?

  • Fetches Wikipedia summaries based on user queries
  • Runs as an MCP-compatible server for AI interactions
  • Utilizes FastAPI and Wikipedia API for efficient data retrieval
  • Quick deployment using Google Colab and Ngrok

use cases of MCP-Wikipedia-API-Server?

  1. Enhancing AI assistants with real-time Wikipedia information
  2. Providing quick answers to user queries in chatbots
  3. Enabling educational tools to fetch summaries for learning purposes

FAQ from MCP-Wikipedia-API-Server?

  • Can this server handle multiple requests?

Yes! The server is designed to handle multiple requests efficiently.

  • Is there a limit to the number of queries?

No, you can send as many queries as needed, but be mindful of the Wikipedia API usage policies.

  • Do I need to pay for using Ngrok?

Ngrok offers a free tier, but for extended usage, a paid plan may be required.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Rishavv007
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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