ArchiveBox API
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host address for HTTP transport | 0.0.0.0 |
| PORT | No | Port number for HTTP transport | 8000 |
| AUTH_TYPE | No | Authentication type: 'none', 'static', 'jwt', 'oauth-proxy', 'oidc-proxy', 'remote-oauth' | none |
| TRANSPORT | No | Transport method: 'stdio', 'http', or 'sse' | stdio |
| EUNOMIA_TYPE | No | Eunomia authorization type: 'none', 'embedded', 'remote' | none |
| TOKEN_ISSUER | No | Issuer for JWT verification | |
| OIDC_BASE_URL | No | Base URL for OIDC Proxy | |
| ARCHIVEBOX_URL | No | URL of the ArchiveBox instance | |
| OAUTH_BASE_URL | No | Base URL for OAuth Proxy | |
| OIDC_CLIENT_ID | No | OIDC client ID | |
| TOKEN_AUDIENCE | No | Audience for JWT verification | |
| TOKEN_JWKS_URI | No | JWKS URI for JWT verification | |
| OIDC_CONFIG_URL | No | OIDC configuration URL | |
| REMOTE_BASE_URL | No | Base URL for Remote OAuth | |
| ARCHIVEBOX_TOKEN | No | Token for token authentication | |
| ARCHIVEBOX_VERIFY | No | Whether to verify SSL certificates | True |
| ARCHIVEBOX_API_KEY | No | API key for API key authentication | |
| EUNOMIA_REMOTE_URL | No | URL for remote Eunomia server | |
| OIDC_CLIENT_SECRET | No | OIDC client secret | |
| ARCHIVEBOX_PASSWORD | No | Password for basic authentication | |
| ARCHIVEBOX_USERNAME | No | Username for basic authentication | |
| EUNOMIA_POLICY_FILE | No | Policy file for embedded Eunomia | mcp_policies.json |
| REMOTE_AUTH_SERVERS | No | Comma-separated list of authorization servers for Remote OAuth | |
| OAUTH_UPSTREAM_CLIENT_ID | No | Upstream client ID for OAuth Proxy | |
| ALLOWED_CLIENT_REDIRECT_URIS | No | Comma-separated list of allowed client redirect URIs | |
| OAUTH_UPSTREAM_AUTH_ENDPOINT | No | Upstream authorization endpoint for OAuth Proxy | |
| OAUTH_UPSTREAM_CLIENT_SECRET | No | Upstream client secret for OAuth Proxy | |
| OAUTH_UPSTREAM_TOKEN_ENDPOINT | No | Upstream token endpoint for OAuth Proxy |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| archivebox_authenticationC | Manage archivebox authentication operations. |
| archivebox_coreD | Manage archivebox core operations. |
| archivebox_cliD | Manage archivebox cli operations. |
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 3 tools
The tool names are distinct (authentication, cli, core), but the descriptions are too generic ('Manage ... operations'), leaving potential overlap between 'cli' and 'core' unclear. An agent might hesitate when choosing between them.
All tools follow a consistent pattern: 'archivebox_' + a noun, making naming fully predictable.
With only 3 tools, the server feels too sparse for a comprehensive API like ArchiveBox, which likely requires more granular operations (e.g., adding URLs, listing archives). The broad categories risk bundling too much functionality.
The tool surface lacks obvious operations such as adding or retrieving archived pages. The vague scopes (cli, core, authentication) suggest many domain operations are missing, leaving agents with limited coverage.