lynx-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Semantic + lexical (hybrid) search over an indexed source. This is your PRIMARY search tool — use it FIRST for any question about the indexed code or docs. Omit |
| deep_searchA | Multi-query fallback search. ESCALATION TOOL — use only when |
| list_sourcesA | List all configured sources with their type, location, chunk count, and drift status. |
| update_source_indexA | Force a full rebuild of a specific source's index. |
| get_rag_statusA | Report state of the RAG index for one source or all sources. |
| feedbackA | Report that you could not find what you needed. Call this BEFORE giving up after exhausting search / deep_search / graph_query. The report is appended to a LOCAL log file on this machine (rag_storage/_feedback/feedback.jsonl) — it is never uploaded anywhere — and helps the index owner tune sources, filters, and chunking. Args: trying_to_do (what you were trying to find or answer); tried (which tools/queries you already tried); stuck (where exactly you got blocked or what was missing). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| guide | How to use Lynx well: search phrasing, score interpretation, escalation ladder, structural queries. |
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/lorenzo-cambiaghi/LynxMCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server