EraseText MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ERASETEXT_API_KEY | Yes | Your EraseText API key, used for authentication. Create one at https://erasetext.com/account/#developer. |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| erase_textA | Erase lettering from a photo or graphic and rebuild the background. Omit the mask to detect all text. White in a mask (channel >127) marks what to erase. Spends 1 EraseText credit only on success. Failures (including 402/504) are not charged. Create a key at https://erasetext.com/account/#developer. Buy prepaid API credits at https://erasetext.com/docs/api/#prepaid. |
| get_accountA | Return API and web credit balances, plan, and this UTC month's usage. Never spends a 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 2 tools
get_account and erase_text have completely distinct purposes: one for account/credit status, one for image text removal. No overlap or ambiguity.
Both tool names use the same verb_noun snake_case pattern (get_account, erase_text), making the API predictable.
With only two tools, the server feels minimal, though it covers the essential operations of the EraseText API. It sits at the thin end of the acceptable range.
The server provides the core account check and erase operations. Minor gaps such as history or preview functionality are absent, but no critical workflow is blocked.