sessemi-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SESSEMI_KEY | Yes | Your Sessemi API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrapeA | Scrape a URL through Sessemi, bypassing Cloudflare, DataDome, and Akamai anti-bot protection. Returns the page content (HTML or JSON depending on the target's Content-Type). Costs credits per request. |
| creditsA | Check your Sessemi API credit balance — remaining credits, tier, and usage. |
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 2 tools
The two tools have completely distinct purposes: 'credits' for checking account balance and 'scrape' for performing web scraping. There is no potential for confusion.
The tool names are simple and clear but not consistent in part of speech: 'credits' is a noun while 'scrape' is a verb. A more consistent pattern like 'check_credits' and 'scrape_url' would improve naming.
Only 2 tools is very minimal for a scraping service. Typically such servers include tools for managing sources, viewing history, or handling different output formats. The count is too low for the implied domain.
The tool surface covers only the basic operations: check credits and perform a scrape. Missing obvious features like listing previous scrapes, cancelling jobs, or configuring output options. Agents would likely encounter dead ends.