Marginalia MCP Server
This server provides an MCP tool to integrate with Marginalia Search, a search engine focused on non-commercial content.
Capabilities include:
Search the web using Marginalia Search API with customizable parameters
Configure searches by specifying indexes and limiting results (1-100)
Utilize an optional API key for potentially higher limits or features
Protection against rate limiting and handling of other errors
Potential to extend functionality by integrating with other MCP servers (like
sayfor text-to-speech)
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Marginalia MCP Serverfind independent blogs about sustainable living"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Marginalia MCP Server
An MCP (Model Context Protocol) server that provides access to Marginalia Search, a search engine focused on finding non-commercial content and hidden gems of the internet.
Features
Search the web using Marginalia Search API
Configurable search parameters including index and result count
Rate limiting protection with helpful error messages
Built using the MCP SDK for seamless integration
Related MCP server: SearxNG MCP Server
Installation
npm install
npm run buildConfiguration
The server can be configured using environment variables:
MARGINALIA_API_KEY: Your Marginalia Search API key (optional, defaults to public access)
To request a dedicated API key, contact: kontakt@marginalia.nu
Usage
The server provides the following MCP tool:
search
Search the web using Marginalia Search with the following parameters:
query(required): Search query stringindex(optional): Search index number (corresponds to dropdown in main GUI)count(optional): Number of results to return (1-100, default: 10)
Example usage through MCP:
const result = await mcp.useTool("marginalia", "search", {
query: "interesting non-commercial websites",
count: 5
});Response Format
The search results are returned in the following format:
{
"query": "your search query",
"license": "license information",
"results": [
{
"url": "result url",
"title": "page title",
"description": "page description"
}
// ... more results
]
}Error Handling
The server includes robust error handling for:
Rate limiting (503 responses)
Invalid requests
Network errors
API-specific errors
Adding Text-to-Speech Support
To enable text-to-speech capabilities using the say MCP server, add the following configuration:
For Cline (VSCode Extension)
Add to ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json:
{
"mcpServers": {
"say": {
"command": "node",
"args": ["/Users/barton/worlds/servers/src/say-mcp-server/build/index.js"]
}
}
}For Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"say": {
"command": "node",
"args": ["/Users/barton/worlds/servers/src/say-mcp-server/build/index.js"]
}
}
}The say MCP server provides text-to-speech capabilities with multiple voices and languages. Available tools:
speak: Read text aloud using specified voice and ratelist_voices: List all available text-to-speech voices
License
MIT License - See LICENSE file for details
Available Tools
1 toolsearch-marginaliaC
Search the web using Marginalia Search
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | Number of results to return | |
| index | No | Search index (corresponds to dropdown in main GUI) | |
| query | Yes | Search query |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Search the web' but fails to describe key behaviors such as rate limits, authentication needs, result format, or error handling. This leaves significant gaps in understanding how the tool operates beyond basic functionality.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise—a single sentence that directly states the tool's function without any fluff or redundancy. It is front-loaded and wastes no words, making it efficient for quick comprehension by an AI agent.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations and output schema, the description is incomplete. It covers the basic purpose but misses critical context like behavioral traits, result format, and error handling. For a search tool with three parameters and no structured output information, this minimal description leaves too many operational details unspecified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, documenting all three parameters (query, count, index) clearly. The description adds no additional semantic context beyond what the schema provides, such as examples or usage tips. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but doesn't need to heavily.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Search the web using Marginalia Search.' It specifies the verb ('Search') and the resource ('the web'), and mentions the specific search engine ('Marginalia Search'). However, since there are no sibling tools, it cannot differentiate from alternatives, which prevents a perfect score of 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It simply states what the tool does without indicating scenarios where it might be preferred or avoided, leaving the agent with no usage direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.0- First observed
search-marginalia
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'search-marginalia' has a clear and distinct purpose of searching the web using Marginalia Search, leaving no room for confusion or misselection.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'search-marginalia' follows a clear verb_noun pattern, and with no other tools to compare, there are no deviations or inconsistencies in naming conventions.
A single tool for a web search server is too few for the apparent scope, as it lacks basic functionality like filtering results, handling pagination, or accessing specific search features. This minimal toolset feels thin and limits the server's utility, making it borderline inadequate for typical search-related tasks.
The tool surface is severely incomplete for a web search domain. While 'search-marginalia' provides a core search function, there are significant gaps such as no ability to refine searches, view result details, or manage search history. This will likely cause agent failures when more complex search operations are needed.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Search the agentic web. 4,100+ sites, 11 tools incl. check_url + verify_mcp for probe-before-use.
Web search, URL content extraction to Markdown, site mapping, and recursive web crawler.
Search indexed websites, read raw page markdown, and score AI visibility for any site.
Search the web, images, videos, news, and local businesses with robust filters, freshness controls…
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables free web searching using Google search results with no API keys required, returning structured results with titles, URLs, and descriptions.1435MIT
- AlicenseBqualityCmaintenanceProvides web search capabilities using SearxNG, allowing AI assistants like Claude to search the web with a privacy-respecting metasearch engine.111MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables web search capabilities within MCP-compatible LLM clients using the Parallel Search API. Designed for daily use and everyday smaller web-search tasks.16-
- AlicenseAqualityDmaintenanceEnables private web search and webpage content extraction using a local SearxNG instance, prioritizing user privacy and autonomy.22MIT
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/bmorphism/marginalia-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server