Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GITHUB_TOKENNoGitHub 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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 knowledgeScope set, only those packages appear.

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.

sources is intersected with knowledgeScope when set.

searchC

Index helper: find refs (prefer after packages/outline, with source=).

Source symbols are evidence only. executable=true only for Molexp bind. sources is intersected with knowledgeScope when set.

suggestA

Optional shortcut: which package pages to read for task.

list_planesA

List the core connection and optional provider planes.

Each row has id, serve_command, when_to_connect, tools_hint, and disableable. molcrafts is always on; only provider planes can be dropped from a client config.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
molcrafts-workspace-context

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MolCrafts/molmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server