Chaprola MCP Server
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chaprola_helloA | Health check — verify the Chaprola API is running |
| chaprola_registerA | Register a new Chaprola account. Returns an API key — save it immediately |
| chaprola_loginA | Login and get a new API key. WARNING: invalidates the previous API key |
| chaprola_check_usernameA | Check if a username is available before registering |
| chaprola_delete_accountA | Delete an account and all associated data. Requires passcode confirmation |
| chaprola_baa_textA | Get the current Business Associate Agreement text and version. Present to human for review before signing |
| chaprola_reportA | Run a published program and return output. No auth required — program must be published first via /publish |
| chaprola_sign_baaA | Sign the BAA. STOP: You MUST call chaprola_baa_text first, show the FULL text to the human, and get their EXPLICIT typed approval before calling this. Never sign automatically. Only needed for PHI — non-PHI data works without a BAA. |
| chaprola_baa_statusA | Check whether the authenticated user has signed the BAA |
| chaprola_importC | Import JSON data into Chaprola format files (.F + .DA). Sign BAA first if handling PHI |
| chaprola_import_urlA | Get a presigned S3 upload URL for large files (bypasses 6MB API Gateway limit) |
| chaprola_import_processB | Process a file previously uploaded to S3 via presigned URL. Generates .F + .DA files |
| chaprola_import_downloadB | Import data directly from a public URL (CSV, TSV, JSON, NDJSON, Parquet, Excel). Optional AI-powered schema inference |
| chaprola_exportB | Export Chaprola .DA + .F files back to JSON |
| chaprola_listB | List files in a project with optional wildcard pattern |
| chaprola_compileA | Compile Chaprola source (.CS) to bytecode (.PR). READ chaprola://cookbook BEFORE writing source. Key syntax: no PROGRAM keyword (start with commands), no commas, MOVE+PRINT 0 buffer model (not PRINT field), SEEK for primary records, OPEN/READ/WRITE/CLOSE for secondary files, LET supports one operation (no parentheses), field addressing via P.field/S.field requires primary_format/secondary_format params. |
| chaprola_runA | Execute a compiled .PR program. Use async:true for large datasets (>100K records) |
| chaprola_run_statusC | Check status of an async job. Returns full output when done |
| chaprola_run_eachA | Run a compiled .PR program against every record in a data file. Like CHAPRPG from the original SCIOS. Use this for scoring, bulk updates, conditional logic across records. |
| chaprola_publishB | Publish a compiled program for public access via /report |
| chaprola_unpublishB | Remove public access from a published program |
| chaprola_export_reportC | Run a .PR program and save output as a persistent .R file in S3 |
| chaprola_downloadA | Get a presigned S3 URL to download any file you own (1-hour expiry) |
| chaprola_queryC | SQL-free data query with WHERE, SELECT, aggregation, ORDER BY, JOIN, pivot, and Mercury scoring |
| chaprola_sortA | Sort a data file by one or more fields. Modifies the file in place |
| chaprola_indexB | Build an index file (.IDX) for fast lookups on a field |
| chaprola_mergeB | Merge two sorted data files into one. Both must share the same format (.F) |
| chaprola_formatA | Inspect a data file's schema — returns field names, positions, lengths, types, and PHI flags |
| chaprola_alterA | Modify a data file's schema: widen/narrow/rename fields, add new fields, drop fields. Transforms existing data to match the new schema. |
| chaprola_optimizeB | Run HULDRA nonlinear optimization using a compiled .PR as the objective evaluator |
| chaprola_optimize_statusA | Check status of an async optimization job |
| chaprola_email_inboxA | List emails in the authenticated user's mailbox |
| chaprola_email_readA | Read a specific email by message_id |
| chaprola_email_sendA | Send an email from your @chaprola.org address. Subject to content moderation |
| chaprola_email_deleteB | Delete a specific email from your mailbox |
| chaprola_searchA | Search the web via Brave Search API. Returns titles, URLs, and snippets. Optional AI-grounded summary. Rate limit: 10/day per user |
| chaprola_fetchA | Fetch any URL and return clean content. HTML pages converted to markdown. SSRF-protected. Rate limit: 20/day per user |
| chaprola_scheduleA | Create a scheduled job that runs a Chaprola endpoint on a recurring cron. Max 10 schedules/user, 15-min minimum interval |
| chaprola_schedule_listA | List all scheduled jobs for the authenticated user with run history and next execution time |
| chaprola_schedule_deleteA | Delete a scheduled job by name |
| chaprola_insert_recordA | Insert a new record into a data file's merge file (.MRG). The record appears at the end of the file until consolidation. |
| chaprola_update_recordA | Update fields in a single record matched by a where clause. If no sort-key changes, updates in place; otherwise marks old record ignored and appends to merge file. |
| chaprola_delete_recordA | Delete a single record matched by a where clause. Marks the record as ignored (.IGN). Physically removed on consolidation. |
| chaprola_consolidateA | Merge a .MRG file into its parent .DA, producing a clean sorted data file. Deletes .MRG and .IGN after success. Aborts if .MRG was modified during the operation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| chaprola-guide | Essential guide for working with Chaprola. Read this before writing any Chaprola source code. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| cookbook | Chaprola language cookbook — syntax patterns, complete examples, and the import→compile→run workflow. READ THIS before writing any Chaprola source code. |
| gotchas | Common Chaprola mistakes — no parentheses in LET, no commas in PRINT, MOVE length must match field width, DEFINE names must not collide with fields. READ THIS before writing code. |
| endpoints | Chaprola API endpoint reference — all 40 endpoints with request/response shapes |
| auth | Chaprola authentication reference — API key model, BAA flow, credential recovery |
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/cletcher/chaprola-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server