MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is MCP Server?

MCP Server is a tool that generates Master Content Plans (MCPs) based on various topics by aggregating resources from the web and organizing them into structured learning paths.

How to use MCP Server?

To use MCP Server, clone the repository, set up a virtual environment, install dependencies, and run the server. You can then generate an MCP by making a GET request to the API with your desired topic.

Key features of MCP Server?

  • Generates learning paths for any topic
  • Web search and scraping for relevant resources
  • Customizable learning paths with multiple nodes
  • Supports multiple languages, focusing on Portuguese
  • Performance optimizations and caching for faster responses
  • TF-IDF based resource relevance filtering
  • YouTube integration for video resources
  • Asynchronous task system for real-time feedback

Use cases of MCP Server?

  1. Creating educational content for various subjects
  2. Assisting in language learning with structured resources
  3. Developing training programs in corporate settings

FAQ from MCP Server?

  • Can MCP Server generate content for any topic?

Yes! It can generate learning paths for a wide range of topics.

  • Is there a limit to the number of resources?

You can specify the maximum number of resources to include in the learning path.

  • How does the caching system work?

The caching system stores results to improve response times for repeated queries.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
View license

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

14 hours ago