Skip to main content
Glama

MCP Server (Streamable HTTP)

MCP server that exposes the Posts & Comments API as tools over Streamable HTTP. No auth on /mcp.

Requires Node 18+ (MCP SDK and Hono depend on it).

Setup

  1. Start the main API (Posts server) first, e.g. on port 3000:

    cd .. && MONGO_URI="mongodb://..." npm start
  2. Install and start the MCP server (default port 3001):

    npm install
    npm start

Related MCP server: MCP Server for Ollama Blog

Configuration

  • API_BASE_URL – Base URL of the Posts API (default: http://localhost:3000).

  • MCP_PORT – Port for this MCP server (default: 3001).

Endpoint

  • POST /mcp – MCP Streamable HTTP endpoint (no authentication).
    MCP clients send JSON-RPC here; the server handles initialization and tool calls.

  • GET /mcp – Returns 405 Method Not Allowed (stateless server, no SSE session).

Tools (with validation)

All tools call the main API and apply the same validation rules.

Tool

Description

Validation

create_post

Create a post

title ≥5, author ≥3, category ∈ tech/finance/lifestyle, body ≥50

list_posts

List all posts

—

get_post

Get one post by ID

—

update_post

Update a post

Same as create_post

delete_post

Delete a post (and its comments)

—

add_comment

Add comment to a post

text ≥10, commenter required

list_comments

List comments for a post

—

Validation errors (e.g. invalid category, body too short) are returned as tool errors with clear messages. If the API returns 404 (e.g. post not found), the tool returns that as an error.

Flow

  1. MCP client sends POST /mcp with JSON-RPC (e.g. initialize, then tools/call).

  2. Server uses Streamable HTTP transport (stateless, new server + transport per request).

  3. Tool handlers validate arguments (Zod + custom rules), then fetch() the Posts API.

  4. API response is returned as the tool result (or an error).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP client interaction via streamable HTTP, providing example tools (echo, getPostsByUser) and resources (posts, users) with pluggable authentication providers.
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible clients to securely interact with the BlogWarp REST API via Streamable HTTP, providing read-only access to posts, notifications, timeline, conversations, and following, plus mutating operations such as drafting, publishing, replying, following, and marking notifications read with explicit confirmation.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      It enables developers to run a Streamable HTTP MCP endpoint with example tools, a README resource, and a REST API route as a customizable foundation for MCP server projects.
      MIT