@gluedly/mcp-server
Official# @gluedly/mcp-server
Model Context Protocol (MCP) server that exposes Gluedly’s public API to AI clients such as Claude Desktop.
## Requirements
- Node.js 18+
- A Gluedly API key
## Environment variables
| Variable | Required | Default |
|---|---|---|
| `GLUEDLY_API_KEY` | Yes | — |
| `GLUEDLY_BASE_URL` | No | `https://gluedly.com/api/v1` |
## Tools
| Tool | Description |
|---|---|
| `gluedly_list_pages` | `GET /pages` — list mapped pages (`id`, `title`, `url`, `next_scrape_date`) |
| `gluedly_trigger_scrape` | `POST /execute` with `{ page_id }` — run a scrape now |
| `gluedly_get_snapshot` | Resolve latest snapshot if needed, then `GET /pages/{page_id}/data/{snapshot_id}` as JSON rows or Markdown |
## Claude Desktop config
Add the server to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"gluedly": {
"command": "npx",
"args": ["-y", "@gluedly/mcp-server"],
"env": {
"GLUEDLY_API_KEY": "YOUR_GLUEDLY_API_KEY"
}
}
}
}
```
Optional custom API host:
```json
{
"mcpServers": {
"gluedly": {
"command": "npx",
"args": ["-y", "@gluedly/mcp-server"],
"env": {
"GLUEDLY_API_KEY": "YOUR_GLUEDLY_API_KEY",
"GLUEDLY_BASE_URL": "https://gluedly.com/api/v1"
}
}
}
}
```
## Local development
```bash
bun install
bun run build
bun run test
GLUEDLY_API_KEY=… node dist/index.js
```
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.