account-pool-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APM_DB_PATH | No | The SQLite file. Same path for every session. | ./account-pool.db |
| APM_ACCOUNTS_FILE | No | Pools + accounts to load on startup. | ./accounts.json |
| APM_LEASE_WAIT_MS | No | 0 = fail fast when the pool is empty; >0 = wait this long for one to free up. | 0 |
| APM_DEFAULT_TTL_SECONDS | No | How long a lease lasts before it's reclaimable. | 1800 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lease_accountA | Lease one account from the pool for browser login, EXCLUSIVELY, until you release it or the lease expires. No other session can be handed the same account while you hold it. You MUST call release_account with the returned lease_token when finished. If your task may run longer than the lease TTL, call renew_lease periodically to keep it. |
| release_accountA | Release a leased account so others can use it. Idempotent: releasing an already-released, expired, or unknown token returns released:false rather than erroring. |
| renew_leaseA | Extend (heartbeat) the current lease so long-running work is not reclaimed out from under you. If the lease already expired and was reclaimed (or the token is unknown), returns renewed:false — do NOT assume you still hold the account; call lease_account again. |
| pool_statusA | Observability for the pools: totals, how many are available vs leased, and per-account state (free / leased / expired). Credential values are NEVER returned. |
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 4 tools
Each tool has a clearly distinct purpose: leasing, checking pool status, releasing, and renewing. No functional overlap between them.
All tool names follow a consistent verb_noun pattern (lease_account, pool_status, release_account, renew_lease). No mixed conventions.
Four tools cover the essential operations for an account pool (acquire, release, renew, status). The count is well-scoped and appropriate.
Core lifecycle is complete: acquire, release, renew, and monitor status. Missing operations like creating or deleting accounts, but those are likely out of scope for a pool manager.