Typst Universe MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_packagesB | Search for Typst packages in the Typst Universe. You can search by query text, filter by category, and specify the kind (packages or templates). |
| get_package_detailsA | Get detailed information about a specific Typst package, including its description, authors, categories, repository link, import code, and version history. |
| list_categoriesA | List all available package categories in Typst Universe. |
| get_featured_packagesB | Get a list of featured/popular packages from Typst Universe. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: get_featured_packages retrieves curated/popular packages, get_package_details provides in-depth information on a specific package, list_categories enumerates available categories, and search_packages enables filtered searching. An agent can easily distinguish between these functions without confusion.
All tool names follow a consistent verb_noun pattern (get_featured_packages, get_package_details, list_categories, search_packages) with clear, descriptive verbs (get, list, search) and nouns (packages, categories). There are no deviations in style or convention.
With 4 tools, this server is well-scoped for its purpose of interacting with the Typst Universe package repository. Each tool earns its place by covering essential operations: browsing featured packages, viewing details, exploring categories, and searching. This count avoids bloat while providing complete core functionality.
The tool set covers the core browsing and discovery workflows for a package repository (list, get details, search, filter by category), with no obvious dead ends. A minor gap exists in the lack of tools for package management actions like installation or version updates, but this is reasonable for a read-only discovery server focused on the Typst Universe.