traylinx-search-engine-mcp-server
OfficialClick 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., "@traylinx-search-engine-mcp-serversearch for latest news on artificial intelligence"
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.
Traylinx Search Engine MCP Server
A Model Context Protocol (MCP) server that acts as a bridge to the deployed Agentic Search API. It allows MCP clients like Claude Desktop and Cursor to utilize intelligent search capabilities with both text summaries and structured data (HTML, images, and more).
Tools
search
Perform a web search using Traylinx's API, which provides detailed and contextually relevant results with citations. By default, no time filtering is applied to search results.
Inputs:
query(string): The search query to perform.search_recency_filter(string, optional): Filter search results by recency. Options: "month", "week", "day", "hour". If not specified, no time filtering is applied.
Related MCP server: agent-web-search-mcp
How it Works
You configure this MCP server with your Agentic Search API URL and API Key (via environment variables passed by the client config).
An MCP client (e.g., Claude) sends a tool call to this server with a search query and optional recency filter.
This MCP server makes a request to the Agentic Search API with the query and authorization header.
It parses the rich response (text, HTML, search results, media, news) and returns structured content to the MCP client.
Installation
Prerequisites
Node.js >= 18.0.0
An API Key from Traylinx.com
Step 1: Get an API Key from Traylinx
Visit traylinx.com and sign up for an account
Navigate to the developer dashboard/API section
Generate your API key for the Agentic Search API
Keep this key secure - you'll need it for configuration
Step 2: Set Up the MCP Server
# Clone the repository
git clone https://github.com/traylinx/traylinx-search-engine-mcp-server.git
cd traylinx-search-engine-mcp-server
# Install dependencies
npm install
# Build the project
npm run buildStep 3: Configure Your MCP Client
For Claude Desktop
Edit your claude_desktop_config.json file:
{
"mcpServers": {
"traylinx-search-engine-mcp-server": {
"command": "node",
"args": ["path/to/traylinx-search-engine-mcp-server/dist/index.js"],
"env": {
"AGENTIC_SEARCH_API_KEY": "sk-lf-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"AGENTIC_SEARCH_API_URL": "https://agentic-search-engines-n3n7u.ondigitalocean.app",
"LOG_LEVEL": "INFO"
}
}
}
}You can access this file at:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
For Cursor
Edit your mcp.json file:
{
"traylinx-search-engine-mcp-server": {
"env": {
"AGENTIC_SEARCH_API_KEY": "sk-lf-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"AGENTIC_SEARCH_API_URL": "https://agentic-search-engines-n3n7u.ondigitalocean.app",
"LOG_LEVEL": "INFO"
},
"command": "node",
"args": ["path/to/traylinx-search-engine-mcp-server/dist/index.js"]
}
}IMPORTANT: Replace the placeholder API key with your actual key from Traylinx.com
Verification
After configuring your MCP client, restart it completely.
Start a new chat and instruct it to use the tool:
"Use the search tool to find information about quantum computing."
"Search for the latest news about artificial intelligence and filter by last week."
"Extract text and HTML from the URL https://traylinx.com"
When the client requests permission, grant it.
You should receive a response containing both text content and potentially structured data.
Advanced Usage
The Traylinx Search Engine MCP Server supports multiple response types:
Text Content: Standard markdown text summarizing the search results
Embedded HTML: For URL extractions, the server can return the scraped HTML
Search Items: Structured search results with title, URL, and snippet
Media Items: Images, videos, and other media found during the search
News Articles: Recent news with thumbnails and metadata
Raw API Response: Complete response data for advanced use cases
Using the Recency Filter
To filter search results by recency:
// Example from Claude Desktop
Use the search tool to find recent news about SpaceX with results from the last day only.
// Example from a custom client
{
"name": "search",
"arguments": {
"query": "SpaceX launches",
"search_recency_filter": "week"
}
}Features
Rich Content Types: Returns multiple content types beyond just text
Time Filtering: Filter results by recency (month, week, day, hour)
Secure API Key Handling: API key stays in environment variables
Configurable Endpoint: Easily switch between API endpoints if needed
Full MCP Compliance: Implements all required MCP server methods
Deployment
Smithery.ai Deployment
This MCP server can be deployed to Smithery.ai:
Create/login to your Smithery account
Click "Deploy a New MCP Server"
Enter ID:
traylinx-search-engine-mcp-serverUse base directory:
.(dot for root)Click "Create"
Once deployed, you can reference this server in Claude's web interface by using:
Use the traylinx-search-engine-mcp-server to search for [your query]Note: You'll need to provide your AGENTIC_SEARCH_API_KEY as an environment variable in the Smithery deployment settings.
Troubleshooting
If you encounter issues:
Check your API key is correctly set in the configuration
Ensure the MCP client has been fully restarted after configuration
Verify network connectivity to the Agentic Search API
Set
LOG_LEVELtoDEBUGfor more detailed logs
For additional support, contact the API provider at support@traylinx.com
License
This project is licensed under the MIT License - see the LICENSE file for details.
Available Tools
1 toolsearchA
Perform a web search using Traylinx's API, which provides detailed and contextually relevant results with citations. By default, no time filtering is applied to search results.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The search query to perform | |
| search_recency_filter | No | Filter search results by recency (options: month, week, day, hour). If not specified, no time filtering is applied. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses the default time filtering behavior (none) but omits other behavioral traits such as rate limits, result count limits, error handling, or expected latency. With no annotations, the description should provide more behavioral context.
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?
Two sentences with no fluff. First sentence provides purpose and key attributes (citations), second sentence clarifies default behavior. Every phrase earns its place.
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?
Adequate for a simple search tool with two parameters and no output schema. Mentions citations and default filtering, but lacks details on result structure, pagination, or potential errors. Could be more comprehensive.
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?
Schema coverage is 100%, so baseline is 3. Description adds no new information beyond the schema; it restates the default for the recency filter but does not enhance understanding of parameters.
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?
Clearly states the tool performs a web search using Traylinx's API, indicating the verb (search) and resource (web). Adds specificity by noting results include citations. With no sibling tools, differentiation is not required.
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?
Implies usage for web search but does not explicitly guide when to use it over alternatives. Mentions default no time filtering, which helps with recency filter decisions, but lacks explicit context or exclusion scenarios.
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.1- First observed
search
TDQS
With only one tool, there is no possibility of confusion between tools. The single tool has a clear and distinct purpose: performing web searches.
The single tool is named 'search', which is a clear verb describing its action. Consistency is inherently maintained with only one tool.
One tool is borderline for a search engine server. While a single search endpoint can be functional, typical search APIs offer additional capabilities like pagination, filtering, or getting specific results, which would benefit from more tools.
The server provides a basic search function but lacks obvious features like time-based filtering, result pagination, or tools to retrieve additional details for specific results. These gaps may limit agent effectiveness in more complex queries.
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
Provides AI assistants with access to Seltz's powerful Web Search capabilities.
Scrape, crawl and search the web for AI agents via MCP.
Live AI-native web search with citations. One tool for every MCP client. Flat per-request pricing.
Search the agentic web. 4,100+ sites, 11 tools incl. check_url + verify_mcp for probe-before-use.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform web searches with full content retrieval and multi-engine provenance, including trust scoring and local corpus persistence, via MCP integration.32Apache 2.0
- FlicenseAqualityCmaintenanceEnables MCP-compatible agents to perform web searches via the agent-web-search engine, returning ranked results with sources.1-
- AlicenseAqualityBmaintenanceEnables AI agents to search the web and fetch webpage content as clean text via MCP, with optional headless rendering for dynamic pages.3MIT
- AlicenseBqualityBmaintenanceEnables AI agents to perform web searches and extract full-text content from web pages via standard MCP tools, with fallback search and semantic reranking.22MIT
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/traylinx/traylinx-search-engine-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server