JsonLink MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JSONLINK_API_KEY | Yes | Your JsonLink API key (required). | |
| JSONLINK_API_URL | No | API base URL. Defaults to https://jsonlink.io. | https://jsonlink.io |
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 |
|---|---|
| url_to_markdownA | Fetch a web page and return its main content as clean Markdown (no navigation, ads or footers). Use this to read articles, docs, blog posts or any page the user mentions. Handles JavaScript-rendered pages. 1 credit. |
| extract_metadataA | Get a URL's title, description, preview images, favicon and site name (Open Graph, Twitter Card and HTML meta tags). Use it to summarize what a link is, build link previews or check SEO tags. Faster and cheaper than reading the whole page. 1 credit. |
| screenshotA | Capture a screenshot of a web page and return the image, so you can see how the page looks. Supports desktop, mobile and full-page captures. Cookie banners are hidden. 2 credits. |
| extract_linksA | List every link on a web page with its anchor text, follow/nofollow and internal/external type. Use it to crawl a site, find pages to read next, or audit links. 1 credit. |
| extract_imagesA | List the images on a web page (including lazy-loaded ones) with URL, format, dimensions and file size. Use it to find photos, logos or product images on a page. 1 credit. |
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 5 tools
Each tool returns a clearly distinct output from a URL (Markdown content, metadata, screenshot, links, images), so an agent can easily select the right one. There is minimal overlap; even metadata vs. markdown is explicitly differentiated by cost/purpose.
Four tools follow a clean verb_noun or verb pattern (url_to_markdown, extract_metadata, extract_links, extract_images), but 'screenshot' is a bare noun, a minor deviation. The set is still highly predictable overall.
Five tools is well-scoped for a URL extraction server, with each tool covering a distinct extraction need. No redundant or trivial tools are present.
The surface covers the main web-page extraction tasks: readable content, metadata, visual capture, links, and images. It lacks raw HTML or text extraction, but those are minor gaps agents can often work around via url_to_markdown.