Figranium MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGRANIUM_API_KEY | Yes | The API key generated from Figranium settings to authorize requests. | |
| FIGRANIUM_BASE_URL | No | The base URL of your Figranium server. Defaults to http://localhost:11345. | http://localhost:11345 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_taskA | Create a complete, fully-configured Figranium automation task including sequential action steps, state variables, anti-bot stealth mechanisms, and optional scheduling. 1. PurposeUse this tool when you need to automate any recurring or complex web-based workflows, including data extraction (scraping), automated form-filling, dashboard testing, or dynamic visual monitoring. Tasks are stored permanently in Figranium and can be executed ad-hoc, triggered via API, or scheduled. 2. Execution ModelFigranium tasks run as a linear sequence of steps defined in the 'actions' array. Actions are processed in order from top to bottom. Control flow steps (such as 'if', 'while', 'repeat') allow loops and branching, while 'on_error' steps define fallback behaviors. Variables represent the state and can be updated dynamically during execution. 3. Comprehensive Step Types
4. Selector Strategy & FallbacksWhen targeting elements, follow this hierarchy of selectors:
5. Edge Cases & Retry Logic
6. Complex Real-World Multi-Step JSON Example: |
| task_listA | List all task IDs, names, and descriptions from Figranium. |
| task_executeA | Execute/run a saved automation task by ID and return its result. |
| execution_listA | List a summary of all past execution records. |
| schedule_listA | List all tasks that have schedules configured (enabled or not). |
| schedule_get_all_statusA | Get overall scheduler status and metadata for all schedules. |
| schedule_get_statusA | Get the detailed schedule status, cron configuration, and next run time for a specific task. |
| schedule_setB | Create or update a schedule for a specific task. |
| schedule_deleteA | Disable and remove the schedule configuration from a specific task. |
| schedule_describeA | Validate and preview/describe a schedule configuration without saving it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Figranium Task JSON Schema v1 | Exposes the full annotated JSON Schema of a Figranium task so agents can inspect the full specification directly. |
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/figranium/figranium-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server