O'Reilly Expert MCP Server

io.github.oreillymediaPublished by GitHub account oreillymediav1.0.0Updated Oct 25, 2026

Grounded, citable answers to tech questions from O'Reilly's library. Requires Expert MCP access.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

A remote MCP server that gives assistants grounded, citable answers to technology questions from O'Reilly's library.

What you can do
Answer technology questions using O'Reilly's library content, with grounded, citable responses. No individual tools are listed in the manifest, so capabilities are described only at this level. Access depends on an O'Reilly Expert MCP entitlement.
When to use it
Useful when you want an assistant's technical answers backed by O'Reilly library material and citations, rather than general model knowledge. It fits research and learning workflows for people with O'Reilly Expert MCP access.
Requirements
A remote endpoint at api.oreilly.com over streamable HTTP; no local package. Authentication is required via OAuth, which OAuth-capable clients start automatically, or an Authorization header token. An O'Reilly Expert MCP access entitlement is needed.
Before you install
You must supply OAuth credentials or an Authorization token, so treat that token as a secret. Access is gated by an O'Reilly Expert MCP entitlement, which may involve a paid subscription. Questions and queries are sent to O'Reilly's remote service.

Installation

In SourceWeft

  1. Open O'Reilly Expert 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-expert/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-expert": {
      "type": "http",
      "url": "https://api.oreilly.com/api/expert/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.0.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.