Skip to main content
Glama
rcdelacruz

Nexus MCP Server

by rcdelacruz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
nexus_searchA
A hybrid search tool combining Exa's breadth and Ref's specificity.

Args:
    query: The search term.
    mode: 'general' for broad web search (Exa style).
          'docs' to prioritize technical documentation (Ref style).
    max_results: Number of results to return (1-20).

Returns:
    Formatted search results with titles, URLs, and snippets.
nexus_readA
Reads a URL with intelligent parsing logic.

Args:
    url: The URL to visit.
    focus:
        'general' = Returns clean article text (Exa style).
        'code'    = Returns only headers, code blocks, and tables (Ref style).
        'auto'    = Detects if it's a doc site and switches to 'code' mode.

Returns:
    Parsed and cleaned content from the URL.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: 'nexus_read' fetches and parses content from a specific URL, while 'nexus_search' performs web searches based on a query. There is no overlap in functionality, and an agent can easily differentiate between them based on whether it needs to retrieve known content or discover new information.

Naming Consistency5/5

Both tools follow a consistent 'nexus_verb' naming pattern, using snake_case throughout. The verbs 'read' and 'search' are distinct and accurately describe their respective actions, creating a predictable and readable naming convention across the tool set.

Tool Count2/5

With only two tools, the server feels under-scoped for its apparent purpose of intelligent web content retrieval and search. This minimal set may limit agents' ability to perform more complex workflows, such as saving, organizing, or analyzing retrieved content, making it borderline too thin for practical use.

Completeness3/5

The tools cover basic retrieval (read) and discovery (search) functions, but there are notable gaps. For example, there is no tool for managing or storing fetched content, no way to interact with search results beyond viewing them, and no update or deletion capabilities, which could hinder agents in more advanced tasks.

Resources