mcp-ragchat

ragchat_serve

Launch a local HTTP chat server on localhost that handles POST /chat requests for a specified domain, enabling RAG-powered AI chat integration for your website.

Instructions

Start a local HTTP chat server for a domain. The server runs on localhost and handles POST /chat requests. Use ragchat_widget to get the embed code that connects to this server.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "ragchat_serve"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain to serve
`port`	No	Port to listen on (default: 3456)

Schema Changelog

Changes observed during successful MCP inspections.

AddedApr 30, 2026

TDQS

A3.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses that the server runs on localhost and handles POST /chat, but does not mention key behaviors such as port occupation, domain validation, or how to stop the server. It adds some value but lacks depth.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise: two sentences with no filler. The first sentence states the primary purpose, and the second provides a sibling pointer. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description is moderately complete. It specifies the HTTP endpoint and mentions a sibling tool, but omits important details such as whether the server runs synchronously, how to stop it, or what the return value is. For a 2-parameter tool, this is adequate but has gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (both parameters have descriptions). The description adds minimal extra meaning by tying the domain parameter to 'domain to serve' and port with default 3456, but essentially repeats schema info. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the tool starts a local HTTP chat server for a domain, specifies the endpoint (POST /chat) and host (localhost). It also distinguishes itself from the sibling tool ragchat_widget, which provides the embed code.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by describing what the tool does, but does not explicitly state when to use it versus other sibling tools (e.g., ragchat_setup, ragchat_status, ragchat_test). It only mentions ragchat_widget for obtaining the embed code, providing limited usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server