Skip to main content
Glama
abicyclerider

semarcy-mcp

by abicyclerider
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VOYAGE_API_KEYYesVoyage AI API key for embedding search queries
SEMARCY_DB_PATHNoOverride ChromaDB storage path (default: ./chroma_data locally, /data/chroma in Docker)./chroma_data

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
search_semarchy_docsB

Search Semarchy documentation (xDM, xDI, xDG) using semantic search.

Args:
    query: Natural language search query about Semarchy products.
    product: Filter by product: "xdm", "xdi", or "xdg". Omit to search all.
    max_results: Maximum number of results to return (default 5).
list_semarchy_topicsA

List available Semarchy documentation topics and products.

Returns an overview of what documentation has been indexed, including products and page counts.

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

A3.6/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one performs semantic searching, the other lists available topics/products for browsing. An agent can easily choose between them.

Naming Consistency5/5

Both names follow a consistent verb_noun pattern (search_semarchy_docs, list_semarchy_topics) and use snake_case uniformly.

Tool Count3/5

Two tools is quite thin for a documentation server; while search and topic listing cover the core, a third tool (e.g., get page by ID) would make the surface more useful.

Completeness3/5

Search and topic listing cover discovery, but there is no way to retrieve a full documentation page by identifier, which is a common need after finding a result. This notable gap limits depth of use.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources