@gluedly/mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GLUEDLY_API_KEY | Yes | Your Gluedly API key | |
| GLUEDLY_BASE_URL | No | Optional custom API base URL | https://gluedly.com/api/v1 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gluedly_list_pagesA | Retrieve all mapped scraping pages in your Gluedly workspace. |
| gluedly_trigger_scrapeA | Trigger an immediate web scrape execution for a specific Gluedly page ID. |
| gluedly_get_snapshotA | Fetch clean extracted rows or prompt-ready Markdown for a page snapshot. |
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
Each tool serves a distinct phase of the scraping workflow: listing pages, triggering a scrape, and fetching snapshot data. There is no functional overlap or ambiguity between the tools.
All tool names follow the same pattern: the 'gluedly_' prefix followed by a verb_noun (list_pages, trigger_scrape, get_snapshot). This makes the tool set highly predictable and easy to navigate.
Three tools is minimal but well-scoped for the server's purpose of interacting with an existing Gluedly scraping workflow. Each tool fills a necessary role, and the count is within the ideal range.
The server covers the essential end-to-end flow: list pages, trigger a scrape, and collect the extracted data. It lacks CRUD/manage capabilities for pages, but this is likely outside the MCP server's intended scope and easily workable.