O'Reilly Media MCP Server

io.github.oreillymediaPublished by GitHub account oreillymediav1.4.0Updated Oct 24, 2026

Search O'Reilly for tech books, courses, events, and more. Requires an O'Reilly subscription.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Lets an assistant search O'Reilly for tech books, courses, events, and more through a remote OAuth-protected endpoint.

What you can do
Connects an assistant to O'Reilly's hosted search service so it can look up tech books, courses, events, and other learning content in the O'Reilly catalog. It runs as a remote endpoint rather than a local package, and authentication is handled through OAuth or an Authorization header.
When to use it
Useful when you want an assistant to find O'Reilly learning material, such as books or courses on a topic, while working in an OAuth-capable client. It is meant for people with an O'Reilly subscription.
Requirements
A remote connection to the O'Reilly API endpoint; no local runtime or packages. An O'Reilly subscription is required. Authentication is OAuth (recommended, handled automatically by OAuth-capable clients) or an Authorization header token. Network access is needed.
Before you install
Access requires an O'Reilly subscription and authentication credentials; the Authorization header carries a token, so keep it private. Search queries are sent to O'Reilly's remote service.

Installation

In SourceWeft

  1. Open O'Reilly Media MCP Server in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.oreillymedia%2Foreilly-mcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "o-reilly-media": {
      "type": "http",
      "url": "https://api.oreilly.com/api/search/v1/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.4.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.