molmcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub token used for authentication when accessing GitHub repositories as sources (e.g., github:owner/repo). |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| infoA | Ops/health view of sources and registry (not the main discovery path). |
| packagesA | L0 directory page: every package + summary for context injection. Read the markdown (or data.packages[].summary) and choose sources yourself — this is a catalog, not a ranking. With |
| outlineB | L1 module directory for one source (optional path prefix). |
| openA | L2 symbol page: signature, doc, examples, tests (inject before coding). Miss → ok=false / SYMBOL_NOT_FOUND. Empty examples are honest zeros. |
| composeB | Bind packages + suggest + explore/open pages into one budgeted pack.
|
| searchC | Index helper: find refs (prefer after packages/outline, with source=). Source symbols are evidence only. executable=true only for Molexp bind.
|
| suggestA | Optional shortcut: which package pages to read for task. |
| list_planesA | List the core connection and optional provider planes. Each row has |
| routeA | Which optional provider plane(s) to connect for task. Routing only — no science. molcrafts is already this connection. Do not invent domain MCP tools for chemistry APIs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| molcrafts-workspace-context |
TDQS
Scored across 9 tools
The main exploration tools are explicitly layered (packages/outline/open), and info/list_planes/route are separated by role. Search, suggest, and compose have closely related purposes, but their descriptions distinguish ref-finding, package-page recommendation, and bundling, so an agent can usually select the right one.
Tool names mix bare nouns (info, packages, outline, open) with verbs (compose, search, suggest, route) and one snake_case verb_phrase (list_planes). There is no consistent verb_noun convention or common prefix, making the surface feel ad hoc despite the underlying hierarchy.
Nine tools is well within the ideal scope for a server of this complexity. Each tool has a distinct function in the discovery, search, composition, health, and routing workflow, with no obvious redundancy.
The browse (packages/outline/open), search, suggest, compose, health, and plane-routing flows form a complete read-only discovery workflow. The only minor gap is the lack of a raw package/registry detail view beyond info and open, but agents can still accomplish the core task.