ETSI Standards Connector
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ETSI_CACHE_DIR | No | Where downloaded PDFs are cached. | ./cache |
| ETSI_STANDARDS_DIR | No | Where summary .md files are written. | ./standards |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_standardA | Search the ETSI standards catalogue. Returns matching standards sorted most-recent first. |
| fetch_standardA | Fetch and parse an ETSI standard PDF. Saves the document text locally and returns summarisation instructions and metadata. Then call read_document_text repeatedly to read the document in chunks, build the summary, and finally call save_summary to persist it. If the standard is already ingested, returns the existing summary immediately. Use refresh=true to re-fetch. |
| read_document_textA | Read a chunk of the extracted text for a standard fetched with fetch_standard. Call repeatedly with the returned next_offset until done is true. |
| save_summaryA | Persist a structured summary to standards/.md. Call this after producing a summary from fetch_standard output. |
| get_summaryA | Read the stored summary for an already-ingested ETSI standard. |
| list_ingestedA | List all ETSI standards that have been ingested and summarised locally. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/magicbadger/claude-mcp-etsi'
If you have feedback or need assistance with the MCP directory API, please join our Discord server