Skip to main content
Glama
manishgadhock-monotype

Monotype MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MONOTYPE_TOKENNoYour Monotype authentication token

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
invite_user_for_customerC

Invite a user for a customer. This is equivalent to creating a user for the customer. The user receives an email invitation and then gets onboarded.

get_teams_for_customerC

Get all teams for a specific customer ID

get_roles_for_customerC

Get all roles for a specific customer ID

get_role_id_by_nameA

Get role ID by role name. Searches through all roles for the customer and returns the role ID if found.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get_role_id_by_name retrieves a specific role ID, get_roles_for_customer lists all roles, get_teams_for_customer lists all teams, and invite_user_for_customer handles user invitations. There is no overlap or ambiguity between these operations.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with underscores, using 'get' for retrieval operations and 'invite' for creation. The naming is predictable and readable across the set.

Tool Count3/5

With only 4 tools, the server feels thin for a customer management domain. While the tools cover basic retrieval and user invitation, the scope suggests more operations (e.g., updating roles/teams, managing users) would be expected, making the count borderline.

Completeness2/5

The toolset has significant gaps for customer management. It lacks update or delete operations for roles, teams, or users, and missing core functions like creating roles/teams or managing user details. This incomplete coverage will likely cause agent failures in common workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues