Prefer the hosted remote MCP URL. Clients authenticate with OAuth 2.1 in the browser; Gluedly rotates a dedicated MCP API key and returns it as the access token. Keep `@gluedly/mcp-server` stdio only when the host cannot use HTTP MCP.
Why teams use this integration
- No long-lived keys pasted into config for HTTP MCP hosts—consent regenerates the MCP API key.
- One remote endpoint works across Cursor, Claude, Codex, and other OAuth-capable MCP clients.
- Local stdio with GLUEDLY_API_KEY remains available for Claude Desktop local config and scripts.
Recommended setup
- Map the pages and fields you want agents to read in Gluedly.
- In your MCP host config, set gluedly.url to https://gluedly.com/mcp (or your app URL + /mcp locally).
- When the client prompts, sign in to Gluedly and approve the requested scopes.
- Use gluedly_list_pages, gluedly_trigger_scrape, gluedly_get_snapshot, and gluedly_fetch_html from the agent.
- Optional fallback: npx @gluedly/mcp-server with GLUEDLY_API_KEY for stdio-only hosts.
Example code
Use the latest structured data from Gluedly as the input layer for your AI stack.
{
"mcpServers": {
"gluedly": {
"url": "https://gluedly.com/mcp"
}
}
}