VectorMCP MCP Server

If you already use VectorMCP, the vectormcp mcp server is the piece that lets your assistant work with it directly. A server implementation for the Model Context Protocol (MCP) in Ruby.

What the server does

VectorMCP is a Ruby implementation of the Model Context Protocol (MCP) server-side specification. It gives you a framework for exposing tools, resources, prompts, roots, sampling, middleware, and security over the MCP streamable HTTP transport.

• Streamable HTTP is the built-in transport, with session management, resumability, and MCP 2025-11-25 compliance
• Class-based tools via VectorMCP::Tool, plus the original block-based register_tool API
• Rack and Rails mounting through server.rack_app
• Opt-in authentication and authorization, structured logging, and middleware hooks
• Request-scoped identity: every request is dispatched through its own invocation, so concurrent requests on one session can never observe each other's headers or auth
• Image-aware tools/resources/prompts, roots, and server-initiated sampling

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Credentials and setup notes

• Ruby 3.2+

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the AI and media services group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by sergiobayona; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against VectorMCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.