Skip to main content
Glama
Exorust

AdKit MCP Server

by Exorust
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MAX_TOP_KNoMax results per match query100
QDRANT_HOSTNoQdrant server hostlocalhost
QDRANT_PORTNoQdrant server port6333
MCP_DATA_KEYNoData API key (required if REQUIRE_DATA_KEY is true)
MCP_ADMIN_KEYNoAdmin API key (required if REQUIRE_ADMIN_KEY is true)
MAX_BATCH_SIZENoMax ads per upsert batch500
REQUIRE_DATA_KEYNoIf true, Data Plane requires MCP_DATA_KEY envfalse
REQUIRE_ADMIN_KEYNoIf true, Control Plane requires MCP_ADMIN_KEY envfalse
EMBEDDING_MODEL_IDNoEmbedding modelBAAI/bge-small-en-v1.5
EMBEDDING_DIMENSIONNoVector dimension384
QDRANT_COLLECTION_NAMENoCollection nameads
REQUEST_TIMEOUT_SECONDSNoPer-request timeout30.0

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
ads_matchA

Match ads by text query. Returns similar ads based on semantic similarity.

Args:
    query: Text query to match against ads
    top_k: Number of results to return (default: 10, max: 100)

Returns:
    JSON string containing list of matching ads with scores and metadata

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.9/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion or ambiguity between tools.

Naming Consistency5/5

With a single tool, there is no inconsistency in naming conventions; the name 'ads_match' is clear and descriptive.

Tool Count2/5

A single tool is too few for a server, making it feel thin and underdeveloped for the ad domain. Even most niche servers benefit from at least a few core operations.

Completeness1/5

Only a search/match function is provided. There are no operations to create, retrieve, update, or delete ads, so the surface is severely incomplete for the stated purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources