Skip to main content
Glama
iamatulsingh

brave-mcp-langchain

by iamatulsingh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchC
Search Brave and return formatted results.

Args:
    query: The search query string
    max_results: Maximum number of results to return (default: 10)
    ctx: MCP context for logging
fetch_contentA
Fetch and parse content from a webpage URL.

Args:
    url: The webpage URL to fetch content from
    ctx: MCP context for logging

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are completely distinct: one performs web searches, the other fetches webpage content. There is no overlap or confusion between their purposes.

Naming Consistency4/5

Both names are verb-based and clear, but 'search' is a single verb while 'fetch_content' follows a verb_noun pattern, showing a minor inconsistency in naming convention.

Tool Count3/5

With only 2 tools, the server feels thin for a search-related service. While these two cover the basic search-and-fetch workflow, the count is on the low end of the borderline range.

Completeness4/5

The core functionality of searching and fetching content is covered, but there are minor gaps such as lack of search result filtering options or pagination controls. Overall, the surface is adequate for simple search tasks.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources