shared-url-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| read_shared_link | Fetches a shared AI chat link (ChatGPT, Claude, Gemini, DeepSeek, Perplexity and others) and writes the full conversation to conversation.md with a metadata.json beside it. Returns a summary and an outline of line numbers instead of the whole transcript, so read the returned file at those lines when you need the detail. |
| inspect_shared_linkA | Reports which provider a share URL belongs to, where it redirects, and whether the link is still reachable. Read-only and fast, so use it to diagnose a link that failed rather than retrying a full extraction. |
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 1 tool
With only one tool, there is no ambiguity whatsoever. The tool's purpose is clearly defined.
A single tool name follows a clear verb_noun pattern, so consistency is perfect.
The server has only one tool, which feels insufficient for the domain of shared URLs. Additional tools (e.g., for sharing or extracting) would be expected.
The tool covers only inspection of shared links. Missing common operations like creating or managing shared links, leaving significant gaps.