Skip to main content

Documentation Index

Fetch the complete documentation index at: https://redop.useagents.site/docs/llms.txt

Use this file to discover all available pages before exploring further.

Redop is a Bun-first TypeScript framework for building production MCP servers.
Hero

Getting Started

Install Redop, scaffold a server, and run your first MCP endpoint over HTTP or stdio.

Core

Understand tools, resources, prompts, plugins, error handling, and lifecycle hooks.

Guides

Follow focused guides for transport choice, auth, plugins, resources, prompts, and debugging.

Reference

Find exact details for the Redop constructor, tool definitions, transports, context, and CLI.

​
What Is Redop?

Redop is a framework for building production MCP servers without hand-writing the transport, session, schema, and lifecycle plumbing yourself. Use it when you want to:
  • define MCP tools with typed handler input
  • validate input with Zod, Standard Schema libraries, TypeBox, or JSON Schema
  • expose resources and prompts from the same server
  • add middleware, lifecycle hooks, and reusable plugins
  • run the same server over HTTP or stdio

​
What Is an MCP Server?

An MCP server is a program that exposes capabilities to MCP clients. In practice, that usually means:
  • tools for actions and workflows
  • resources for readable data addressed by URI
  • prompts for reusable prompt material
  • protocol-level metadata, session handling, and capability discovery
Redop gives you those primitives through one framework API instead of making you implement the protocol plumbing by hand.

​
Why Bun?

Redop is Bun-first, which means the default developer experience assumes you are running your server with Bun. Bun fits Redop well because it gives you:
  • a fast TypeScript-friendly runtime
  • a simple local development loop
  • a single toolchain for installing, running, and shipping the server
bun add @redopjs/redop zod
bun run --watch src/index.ts

​
What You Build With Redop

Tools

Define actions with names, descriptions, schemas, annotations, hooks, middleware, and handlers.

Resources

Expose readable data through static or template URIs, with optional subscriptions.

Prompts

Package reusable prompt material with names, descriptions, arguments, and messages.

Plugins

Reuse hooks, middleware, tools, resources, and prompts as one composable unit.
Redop scales cleanly when you split a larger server into feature modules and compose them with .use(...).

​
Quick Example

import { Redop } from "@redopjs/redop";
import { z } from "zod";

new Redop({
  serverInfo: {
    name: "docs-server",
    title: "Docs Server",
    version: "0.1.0",
    description: "Search docs and return answers.",
  },
})
  .tool("search_docs", {
    description: "Search internal docs",
    inputSchema: z.object({
      query: z.string().min(1),
    }),
    handler: ({ input }) => {
      return {
        query: input.query,
        results: [],
      };
    },
  })
  .listen(3000);
For a hosted server, the MCP endpoint will be available at http://localhost:3000/mcp.

​
Start Here