alpha-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALPHA_MCP_GIT | No | Source setup registers in the clients | |
| ALPHA_MCP_SSH | No | --ssh program name | ssh |
| ALPHA_MCP_TABLES | No | Comma-separated allowlist of queryable tables; empty = all | |
| ALPHA_MCP_DB_LOCAL | No | Local replica | ~/.local/share/alpha-mcp/Global.db |
| ALPHA_MCP_ENV_FILE | No | Explicit .env path, checked first | |
| ALPHA_MCP_DB_ORIGIN | Yes | [USER@]HOST:PATH of the live DB | |
| ALPHA_MCP_SYNC_ARGS | No | Extra args, e.g. --protocol 1, --port 2222 | |
| ALPHA_MCP_DB_MAX_AGE | No | Auto-sync when the replica is older than this; 0 disables | 21600 |
| ALPHA_MCP_REMOTE_EXE | No | --exe on the origin host; leave empty for a local-file origin | |
| ALPHA_MCP_USER_AGENT | No | User-Agent for document downloads | browser-like |
| ALPHA_MCP_SYNC_TIMEOUT | No | Seconds | 600 |
| ALPHA_MCP_EXPORT_SKILLS | No | codex or claude: export prompts as skills on every launch | |
| ALPHA_MCP_SQLITE3_RSYNC | No | Local binary name or full path | sqlite3_rsync |
| ALPHA_MCP_MATERIALS_ROOT | No | Local root for fund documents | ~/.local/share/alpha-mcp/Materials |
| ALPHA_MCP_SYNC_VERBOSITY | No | Keep -vv or more: below that the remote command gets 2>/dev/null, which cmd.exe on a Windows origin rejects | -vvv |
| ALPHA_MCP_DATASETS_PREFIX | No | Prefix stripped from DataSet paths when mapping to the local root | Z:\DataSets |
| ALPHA_MCP_DOWNLOAD_MAX_MB | No | Per-document download limit | 50 |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sync_dbA | Replicate the latest Global.db from the origin host with sqlite3_rsync over ssh. |
| list_tablesA | List queryable tables with their primary key, columns and row counts. |
| get_rowA | Fetch one row from a table by key. Returns {'found': false} when there is no match. |
| find_rowsA | Fetch every row where column = value (read-only). |
| update_fundA | Write verified fields for one fund to the local replica. Only send values you are certain of. |
| chatgpt_response_schemaD | The exact key list (and one example) that ChatGPTResponse values must follow. |
| finish_provider_reviewA | Stamp the provider's LastReviewDate (YYYY-MM-DD HH:MM:SS). Never changes ReviewFinished. |
| list_materialsB | Documents already stored for a fund, and where its Materials directory is. |
| save_materialA | Download one document into the fund's Materials directory. Never overwrites earlier documents: identical content is reported as 'duplicate', changed content is stored under a dated name. |
| get_promptA | Fallback for clients without MCP prompt support: returns the rendered prompt text to follow. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| fund_provider_review | Resolve identifiers, documents and index details for every fund of one provider in FundsDataSets, store the documents, and update the database. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools have clear distinct purposes, but update_fund and finish_provider_review could be confused if both can modify LastReviewDate. The auxiliary tools (get_prompt, chatgpt_response_schema) are clearly separate from data operations.
All names are lowercase snake_case, mostly following verb_noun pattern (list_materials, save_material, sync_db). The one exception is chatgpt_response_schema, which is a noun phrase, deviating from the otherwise consistent verb-noun style.
With 10 tools, the server is well-scoped for its purpose—managing fund data, materials, and database sync. Each tool serves a distinct function without excess, and the count falls within the ideal range.
The core workflows (syncing, updating funds, saving materials, querying rows) are covered, but there are gaps: no tool for deleting materials or funds, no explicit creation of funds (only sync), and provider review only has a 'finish' operation. Generic query tools partially compensate, but lifecycle coverage is incomplete.