aparser-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Health-check the A-Parser server. Returns "pong" when reachable. |
| infoA | Get A-Parser status: tasks in queue, pid, and the list of available parsers. |
| list_parsersA | List the names of all installed parsers (e.g. "SE::Google", "SE::Google::Suggest"). |
| parser_infoA | Describe a parser's result fields. Returns the |
| get_proxiesA | Get live proxies from the proxy checkers as {"ip:port": ["type", ...]}. |
| one_requestA | Run a single parse synchronously and return the result immediately. Best for one-off lookups (a suggest query, one SERP, one page). For many queries or saved output files, use add_task instead.
raw_results=true -> structured |
| add_taskB | Queue a bulk parsing task. Returns the task id (taskUid). Poll it with task_state / wait_task, then fetch the output with task_results.
parsers: stack as a list of [parser_name, preset_name, ...overrideObjects], e.g. [["SE::Google","default"]]. |
| task_stateB | Get a task's status and live stats (status, queriesDone, resultsCount, ...). |
| wait_taskB | Poll a task until it completes (or the timeout elapses). Returns the final state. |
| task_resultsA | Get a single-use download URL for a completed task's results file. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/izzipizzy/aparser-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server