Algora 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_bountiesA | List open bounties on Algora. Optionally filter by organization slug, status, minimum/maximum amount in USD, or tech stack. Returns paginated results with reward amounts and issue URLs. |
| get_org_bountiesB | Get all open bounties for a specific organization on Algora. Use this to check if a known project (cal.com, supabase, etc.) has active bounties you can claim. |
| search_bountiesA | Search open bounties by keyword. Searches titles, descriptions, repo names, and org handles. Useful for finding bounties in a specific domain (e.g., 'database', 'MCP', 'authentication'). |
| get_top_bountiesA | Get the highest-value open bounties on Algora, sorted by reward descending. Perfect for finding the most lucrative opportunities first. |
| get_bounty_statsA | Get aggregate statistics about open bounties: total count, combined value, average amount, breakdown by tech stack, and breakdown by organization. Useful for understanding the overall bounty landscape. |
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 5 tools
Tools are largely distinct, but get_org_bounties is essentially a filtered version of list_bounties, causing minor overlap. Overall, agents can distinguish purposes.
All tools follow a consistent verb_noun pattern (get/list/search + bounties/stats), making predictions easy.
5 tools cover the querying needs for bounties without being excessive or minimal. Well-scoped for the domain.
The set covers key query operations (stats, filter, search, top). Missing a single-bounty detail tool, but the surface is otherwise complete for retrieval.