@aauth/praca
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRACA_PS_URL | No | Person Server URL (default: from local-keys agent config) | |
| PRACA_AGENT_URL | No | Agent provider URL (default: first configured) | |
| PRACA_AGENT_TOKEN | No | Agent token for software-identity override (used with PRACA_AGENT_PRIVATE_JWK) | |
| PRACA_REGISTRY_URL | No | Registry URL (default https://registry.aauth.dev) | https://registry.aauth.dev |
| PRACA_AGENT_KEY_FILE | No | Path to agent key file for software-identity override (alternative to PRACA_AGENT_PRIVATE_JWK) | |
| PRACA_AGENT_PRIVATE_JWK | No | Agent private JWK for software-identity override (used with PRACA_AGENT_TOKEN) |
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 |
|---|---|
| find_resourcesA | Search the AAuth registry for discoverable resources by free-text query against name/description. Returns each result tagged Currently added resources: no resources added yet |
| add_resourceA | Add an AAuth resource to your local set. Pass a bare host, host:port, or full URL — the agent proxy canonicalizes. Fetches the resource's well-known doc, validates, picks supported vocabularies. After adding: agent-token resources are immediately invokable; auth-token resources start an authorization flow on the first Currently added resources: no resources added yet |
| list_resourcesA | Return your locally added resources with name, description, access_mode, last_used, and how many vocabularies the agent proxy picked. Cheap; safe to call anytime. |
| remove_resourceA | Remove a resource from your local set. Agent-proxy-local only — does NOT revoke any user grants at the Person Server; re-adding picks up existing grants transparently. Currently added resources: no resources added yet |
| list_operationsA | List operations a resource exposes. Optional Currently added resources: no resources added yet |
| get_operationsA | Batch fetch full schemas (params, request body, response) for one or more operations on a resource. Separate from list_operations because schemas dominate token cost. Currently added resources: no resources added yet |
| invokeB | Invoke an operation on a resource. Pass Currently added resources: no resources added yet |
| reset_tokensA | Clear all stored upstream OAuth tokens for a resource. Use during testing to force a fresh upstream OAuth flow without touching PS consent state. Currently added resources: no resources added yet |
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 8 tools
Each tool has a distinct purpose: find_resources searches the registry while list_resources shows local additions; list_operations provides summaries while get_operations fetches full schemas; invoke and reset_tokens serve unique actions. No two tools overlap in a way that would confuse an agent.
Most tool names follow a consistent verb_noun snake_case pattern (find_resources, add_resource, list_resources, etc.), but 'invoke' is a lone verb without an object, which is a minor deviation from the established convention.
With 8 tools, the set is well-scoped for managing AAuth resources and their operations. It covers discovery, local management, operation introspection, invocation, and token reset without unnecessary bloat.
The tool surface provides end-to-end coverage: resource discovery and CRUD (find/add/list/remove), operation exploration (list/get schemas), invocation (invoke), and testing support (reset_tokens). No obvious gaps that would block typical workflows.