langextract-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | No | API key for OpenAI provider (required when LANGEXTRACT_MCP_PROVIDER=openai). | |
| LANGEXTRACT_API_KEY | No | API key for Gemini provider (required when LANGEXTRACT_MCP_PROVIDER=gemini). | |
| LANGEXTRACT_MCP_MODEL | No | The model to use for inference (optional). | |
| LANGEXTRACT_MCP_PROVIDER | No | The inference provider to use. Options: sampling, gemini, openai, ollama. Defaults to sampling. | sampling |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| langextract_extractC | Extract structured entities from literal text and return grounded spans. |
| langextract_visualizeB | Render an annotated-document payload as escaped interactive HTML without file access. |
| langextract_statusA | Return safe server configuration, limits, and provider mode without probing providers. |
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 3 tools
The three tools serve clearly distinct purposes: extraction, server status, and visualization. There is no overlap in functionality, and an agent can easily select the right tool based on the task.
All tools share the consistent 'langextract_' prefix followed by a single word. However, 'extract' and 'visualize' are verbs while 'status' is a noun, a minor deviation from a pure verb_noun pattern.
Three tools is well within the typical 3-15 range and each tool has a clear, non-redundant role. The server is focused and does not appear to have unnecessary or missing tools for its scope.
The core extraction, status, and visualization operations are covered, providing a complete basic workflow. Minor gaps exist, such as batch extraction, schema listing, or configuration updates, but agents can work around them.