Skip to main content
Glama
CatMapper MCP

CatMapper MCP

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CATMAPPER_API_KEYYesYour CatMapper API key, used by the MCP server to authenticate with the CatMapper API.
CATMAPPER_API_URLNoOptional CatMapper API base URL. Defaults to https://api.catmapper.org. Use an HTTPS origin for another CatMapper deployment; plain HTTP is allowed only for localhost development.https://api.catmapper.org

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_categoriesC

Search categories and entities. Database is ArchaMap or SocioMap; contexts and dataset are CMIDs.

get_nodeB

Get a node's properties and USES relationships by CMID.

get_node_pageC

Get the explore-page representation of a CatMapper node.

get_datasetC

Get a dataset's details and category data; optionally filter by domain.

list_datasetsC

List datasets in a CatMapper database.

list_domainsC

List public domains in a CatMapper database.

list_subdomainsB

List public subdomains in a CatMapper database.

list_propertiesC

List metadata properties in a CatMapper database.

translateC

Translate tabular category data synchronously. The CatMapper API may log returned rows.

upload_statusB

Check a queued upload's status and progress using its task ID.

preview_mergeA

Preview a category merge and identify cyclic parent references. Does not apply the merge.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 11 tools

Disambiguation4/5

Most tools target clearly distinct resources or actions, such as listing datasets versus searching categories. The main potential confusion is between get_node and get_node_page, which both retrieve node representations but at different levels of detail.

Naming Consistency4/5

Names consistently use snake_case and mostly follow a predictable verb_noun pattern: list_*, get_*, search_*, and preview_*. Minor deviations are translate as a verb-only name and upload_status as a noun phrase, but the overall convention is readable and stable.

Tool Count5/5

With 11 tools, the surface is well-scoped for a database exploration and data-processing server. Each tool appears to cover a distinct operation rather than bloating the set with redundant variants.

Completeness3/5

Core read, search, listing, and translation workflows are covered, but there are notable lifecycle gaps. preview_merge does not apply merges, upload_status exists without an upload-initiating tool, and there are no create/update/delete operations for the main data entities.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues