Server data from the Official MCP Registry
Search Shakespeare monologues, plays, paraphrases and summaries from shakespeare-monologues.org
About
Search Shakespeare monologues, plays, paraphrases and summaries from shakespeare-monologues.org
Remote endpoints: streamable-http: https://mcp.shakespeare-monologues.org/mcp
Security Report
A well-designed, read-only MCP server with proper authentication via public APIs and no dangerous code patterns. The server has appropriate error handling, input validation via Zod, and no credential exposure. Minor concerns around analytics third-party dependencies and PostHog integration do not materially impact security for a read-only service. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 1 high severity). Package verification found 1 issue.
5 files analyzed · 8 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
How to Install & Connect
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
Documentation
View on GitHubFrom the project's GitHub README.
Shakespeare's Monologues — MCP server
A small, read-only Model Context Protocol server that lets MCP-capable AI clients search and fetch Shakespeare monologue metadata from shakespeare-monologues.org.
It's a thin, stateless wrapper over the site's public JSON index
(/api/monologues.json) — no database, no secrets. Every result carries the
monologue's permalink url (where the full text, scene context, and modern-English
paraphrase live) and an attribution note.
Tools
| Tool | What it does |
|---|---|
search_monologues | Free-text search (character / play / first line) + filters: gender, play, style, act, limit. |
get_monologue | One monologue's index entry by numeric id. |
random_monologue | A random monologue, optional gender / play filters. |
list_plays | Every play with its classification and monologue count. |
list_all_monologues_for_a_character | Every monologue spoken by a named character. |
get_monologue_of_the_day | The current Monologue of the Day (latest social post). |
get_paraphrased_monologue | A monologue's full text + its modern-English paraphrase (AI-generated; may be null if not yet generated). |
get_scene_summary | AI-generated summary of the scene a monologue is in (by monologue id). |
get_play_summary | AI-generated summary of a play (by title). |
The paraphrase and summaries are AI-generated (Claude) and only partially cached so far, so those tools return
nullwhere content hasn't been generated yet.
Run locally
Two transports, same tools. server.ts builds the tool surface and knows
nothing about how it's reached; index.ts serves it over HTTP and stdio.ts
over stdio.
Over stdio, the way an MCP client spawns a local server:
npx shakespeare-monologues-mcp
Over HTTP, which is how the hosted instance runs:
npm install
npm run build
npm start # listens on :3000, POST /mcp (set PORT to change)
Health check: GET /health → {"ok":true}.
Neither mode needs credentials — the server reads the site's public JSON index.
Set MONOLOGUES_API_URL to point it elsewhere, and POSTHOG_PROJECT_API_KEY=""
to disable analytics.
Connecting a client
Remote MCP means users add a URL, no install. In a client that supports remote / custom MCP servers (Claude Desktop connectors, etc.), add:
https://mcp.shakespeare-monologues.org/mcp
Or run it yourself over stdio, with no hosted dependency:
{
"mcpServers": {
"shakespeare-monologues": {
"command": "npx",
"args": ["-y", "shakespeare-monologues-mcp"]
}
}
}
For clients configured with a JSON config file, use the streamable-HTTP transport:
{
"mcpServers": {
"shakespeare-monologues": {
"type": "streamable-http",
"url": "https://mcp.shakespeare-monologues.org/mcp"
}
}
}
For a client that only speaks stdio, bridge to the remote server with
mcp-remote:
{
"mcpServers": {
"shakespeare-monologues": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.shakespeare-monologues.org/mcp"]
}
}
}
Note on "autonomous" use: there's no mechanism today for an arbitrary agent to discover and use this with zero user action — a client/platform still has to connect it. For truly zero-setup access, agents can hit the plain JSON API (
/api/monologues.json) and/llms.txtdirectly.
License
- Code: MIT.
- Data served through it: © shakespeare-monologues.org, CC BY-NC-SA 4.0 — please keep the attribution that each tool response includes.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
MarkItDown
Freeby Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
