cmt-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CMT_CACHE | No | Override the local SQLite cache path (defaults to .cache/cmt.db) used for change tracking with get_delta. | |
| CMT_EMAIL | Yes | Your CMT (Microsoft CMT) account email address, used for the plain HTTP login. | |
| CMT_PASSWORD | Yes | Your CMT account password, used for the plain HTTP login. Accounts that require SSO/MFA are not supported. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_my_conferencesB | List conferences the logged-in CMT user participates in (id, name, UrlSegmentName, dates, location). |
| search_conferencesB | Search ALL CMT conferences (~10k) by name, city, country or UrlSegmentName. Paged via top/skip. |
| list_submissionsA | List the user's submissions with status. conference: UrlSegmentName (e.g. 'MyConf2026'). If omitted, pulls submissions across ALL of the user's conferences. Returns a compact status overview (no abstract/files; use get_submission for those). Results are cached for 15 min; set refresh=true to force a live fetch. |
| get_deltaA | What changed since the last time get_delta was called: status changes, newly posted reviews, and newly appearing submissions. Always fetches live data. conference: optional UrlSegmentName (default: all of the user's conferences). The very first call only records a baseline and returns no changes. acknowledge=false peeks without moving the baseline forward. |
| get_submissionC | Full submission summary: authors, abstract, files, subject areas, question answers, dates. |
| get_reviewsB | Reviews (and their question/answer text) visible to the author for a submission. |
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 6 tools
Each tool targets a clearly distinct purpose: listing the user's conferences vs. searching all conferences, listing compact submission statuses vs. fetching full submission details, reviewing changes over time, and retrieving reviews. There is no meaningful overlap that would cause misselection.
All tool names use a consistent snake_case verb_noun pattern (list_*, search_*, get_*). The only small variation is the modifier in list_my_conferences, but it still follows the same readable convention.
Six tools is well-scoped for a focused CMT client covering conferences, submissions, reviews, and change tracking. Each tool earns its place without redundant bulk.
The surface covers core read-only author workflows: finding conferences, listing submissions, inspecting a submission, getting reviews, and tracking deltas. Minor gaps remain, such as no direct submission search or standalone conference-detail lookup, but agents can largely work around these.