Data · Remote MCP server
Shakespeare's Monologues
Search Shakespeare monologues, plays, paraphrases and summaries from shakespeare-monologues.org.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.slshults/shakespeare-monologues- Version
- 0.1.2
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-08-31
- Updated
- 2026-08-31
- Publisher
- slshults (GitHub) · 2 servers with pages here
- Website
- www.shakespeare-monologues.org
- Repository
- github.com/slshults/shakespeare-monologues-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.shakespeare-monologues.org/mcp | None |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | shakespeare-monologues-mcp | 0.1.0 | stdio |
How to connect Shakespeare's Monologues
Shakespeare's Monologues is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.shakespeare-monologues.org/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: shakespeare-monologues-mcp version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y shakespeare-monologues-mcp@0.1.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"shakespeare-monologues": {
"command": "npx",
"args": [
"-y",
"shakespeare-monologues-mcp@0.1.0"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from slshults (GitHub)
| Server | Runs |
|---|---|
| Guitar Practice Routine App — Chord ChartsLook up a guitar chord by name and get a text chord diagram. 12,708 standard-tuning names. | Remote & Local · HTTP, stdio |
More data servers
| Server | Runs |
|---|---|
| sf-intelligence — Salesforce org intelligence for AI agentsOffline, read-only MCP knowledge base for one Salesforce org's metadata, deps & impact. | Local · stdio |
| Sgdata MCPSingapore government data for AI agents: ACRA, HDB, COE, URA, SingStat, MAS, IRAS. 87 tools. | Local · stdio |
| ShadeSearch, inspect, organize, annotate, share, and automate creative assets in Shade. | Remote · HTTP |
| ShadowCrawlStealth scraping & search. Bypasses Cloudflare, DataDome & LinkedIn via Cyborg HITL approach. | Remote · HTTP |
| SHAR Public Knowledge MCPAnonymous read-only access to source-backed public SHAR Production knowledge. | Remote · HTTP |
| ShareSend a web page to specific people, control who opens it, see how it was read, and update it. | Remote & Local · HTTP, stdio |
| ShareCut QR & Short LinksShort links you can re-point after printing the QR, with click analytics. Free QR, no key. | Remote & Local · HTTP, stdio |
| Shared PersistencePersistent shared message space for autonomous agents: read, write, reply, search. Free, no signup. | Remote · HTTP |